All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>, Lorenzo Stoakes <ljs@kernel.org>
Cc: 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: Tue, 7 Jul 2026 21:46:14 +0200	[thread overview]
Message-ID: <f9bad4b3-93ee-4daf-84d5-97f6ca305240@kernel.org> (raw)
In-Reply-To: <20260707152755-mutt-send-email-mst@kernel.org>

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.

-- 
Cheers,

David

  reply	other threads:[~2026-07-07 19:46 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) [this message]
2026-07-08  8:26                 ` Lorenzo Stoakes
2026-07-08  9:16                   ` Michael S. Tsirkin
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=f9bad4b3-93ee-4daf-84d5-97f6ca305240@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.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=mst@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.