From: "Michael S. Tsirkin" <mst@redhat.com>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Sourav Panda <souravpanda@google.com>,
muchun.song@linux.dev, osalvador@suse.de,
akpm@linux-foundation.org, liam@infradead.org, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
mhklinux@outlook.com, fvdl@google.com, gthelen@google.com,
mike.kravetz@oracle.com, pasha.tatashin@soleen.com,
rientjes@google.com, riel@surriel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [RFC PATCH 0/6] mm/hugetlb: Dynamic, NUMA-aware HugePage Cache & Free Page Reporting
Date: Wed, 8 Jul 2026 05:16:00 -0400 [thread overview]
Message-ID: <20260708050547-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <ak4JiBcvi29sYx0v@lucifer>
On Wed, Jul 08, 2026 at 09:26:18AM +0100, Lorenzo Stoakes wrote:
> On Tue, Jul 07, 2026 at 09:46:14PM +0200, David Hildenbrand (Arm) wrote:
> > On 7/7/26 21:32, Michael S. Tsirkin wrote:
> > > On Tue, Jul 07, 2026 at 07:46:28PM +0100, Lorenzo Stoakes wrote:
> > >> On Tue, Jul 07, 2026 at 10:01:55AM -0400, Michael S. Tsirkin wrote:
> > >>>
> > >>> Fair enough.
> > >>>
> > >>>
> > >>> Lorenzo, do you know *how* you want it reworked? Could you write it up
> > >>> at a high level?
> > >>> Because if not, it's not really practical to make it the asking price.
> > >>
> > >> Michael, you're an experienced maintainer, I'm surprised I have to tell you that
> > >> the burden for that lands on the submitter.
> > >
> > > Oh sure, "fix bugs A,B,C before you add to this mess" is a classic way
> > > to actually not end up with even more of a mess. But I usually do try
> > > to be explicit of what are specific issues I want submitter to address.
> > > I don't really feel figuring that out lands on the submitter.
> >
> > Sometimes it's certainly easier. With things like hugetlb there often just isn't
> > a feasible way to integrate it nicely into core-mm. It's just too special.
>
> Yeah exactly :) once you reach a certain level of 'specialness' it is more like
> pointing at a flaming trash pile and crying ;)
>
> >
> > --
> > Cheers,
> >
> > David
>
> Cheers, Lorenzo
Well as long as I'm not the one being asked to put it out ... it is just
hard for me to get motivated to do cleanups if there's no actual bug to
fix, or a feature to develop somewhat proportional in size to the
cleanup. But for example, and without calling anything trash, after poking
at memory-failure.c, *I* want to cry, because either there's multiple
races, or I just don't understand the code. Some of these we discussed
here already.
It seems to boil down to the fact that when people start getting lots of
these errors they rush out and buy a new system, so hey. But maybe with
RAM prices spiking it will become less practical. I'll put together an
email with a list later, maybe.
--
MST
next prev parent reply other threads:[~2026-07-08 9:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 6:42 [RFC PATCH 0/6] mm/hugetlb: Dynamic, NUMA-aware HugePage Cache & Free Page Reporting Sourav Panda
2026-07-07 6:42 ` [PATCH 1/6] mm/hugetlb: add Kconfig and basic cache infrastructure Sourav Panda
2026-07-07 6:42 ` [PATCH 2/6] mm/hugetlb: implement cache recycling and allocation Sourav Panda
2026-07-07 6:42 ` [PATCH 3/6] mm/hugetlb: add sysfs interfaces for cache Sourav Panda
2026-07-07 6:42 ` [PATCH 4/6] mm/hugetlb: add memory shrinker " Sourav Panda
2026-07-07 6:42 ` [PATCH 5/6] Documentation/admin-guide/mm/hugetlbpage.rst: document cache interfaces Sourav Panda
2026-07-07 6:42 ` [PATCH 6/6] mm/hugetlb: support free page reporting for cached hugepages Sourav Panda
2026-07-07 7:18 ` Michael S. Tsirkin
2026-07-07 10:18 ` Michael S. Tsirkin
2026-07-07 6:56 ` [RFC PATCH 0/6] mm/hugetlb: Dynamic, NUMA-aware HugePage Cache & Free Page Reporting Michael S. Tsirkin
2026-07-07 7:21 ` Sourav Panda
2026-07-07 7:29 ` David Hildenbrand (Arm)
2026-07-07 8:09 ` Muchun Song
2026-07-07 10:25 ` Michael S. Tsirkin
2026-07-07 10:28 ` David Hildenbrand (Arm)
2026-07-07 11:06 ` Lorenzo Stoakes
2026-07-07 14:01 ` Michael S. Tsirkin
2026-07-07 18:46 ` Lorenzo Stoakes
2026-07-07 19:32 ` Michael S. Tsirkin
2026-07-07 19:46 ` David Hildenbrand (Arm)
2026-07-08 8:26 ` Lorenzo Stoakes
2026-07-08 9:16 ` Michael S. Tsirkin [this message]
2026-07-09 6:15 ` Sourav Panda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260708050547-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=fvdl@google.com \
--cc=gthelen@google.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhklinux@outlook.com \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox