[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70841ec1-0d14-4fc3-a2be-fd5640f9670d@lucifer.local>
Date: Wed, 30 Jul 2025 16:23:39 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: David Hildenbrand <david@...hat.com>
Cc: Baolin Wang <baolin.wang@...ux.alibaba.com>, akpm@...ux-foundation.org,
hughd@...gle.com, willy@...radead.org, ziy@...dia.com,
Liam.Howlett@...cle.com, npache@...hat.com, ryan.roberts@....com,
dev.jain@....com, baohua@...nel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] mm: shmem: fix the strategy for the tmpfs 'huge='
options
On Wed, Jul 30, 2025 at 11:30:20AM +0200, David Hildenbrand wrote:
> There were opinions in the past that tmpfs should just behave like any other
> fs, and I think that's what we tried to satisfy here: use the write size as
> an indication.
Indeed, it feels like we have too much 'special snowflake' stuff for shmem
anyway. Each instance of those adds more ways to get bugs/unexpected
behaviour.
Powered by blists - more mailing lists