From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Gregory Price (Meta)" <gourry@gourry.net>
Cc: Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Zi Yan <ziy@nvidia.com>, Joshua Hahn <joshua.hahnjy@gmail.com>,
Rakie Kim <rakie.kim@sk.com>,
Ying Huang <ying.huang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] mm/mempolicy: limit shared policy ranges per inode
Date: Mon, 16 Nov 2026 23:17:04 +0100 [thread overview]
Message-ID: <8e63a932-ede9-4751-9181-5ae25815ce0e@kernel.org> (raw)
In-Reply-To: <179484562114.482102.7068121367282977254.b4-reply@b4>
On 11/16/26 17:13, Gregory Price (Meta) wrote:
> On 2026-11-15 17:40 +0100, David Hildenbrand (Arm) wrote:
>> On 11/14/26 21:25, Gregory Price (Meta) wrote:
>>>
>>> Just want to make sure the bases are covered.
>>>
>>
>> Yes, and I'd be very happy to learn about use cases.
>>
>> Maybe we can let this stay in -next for a while before moving forward with this?
>>
>
> Seems reasonable, although just kind of delaying the inevitable.
>
> I suppose the mitigation for it causing issues is backporting an
> increase to the default size.
>
> Eh, if the concern here isn't a big deal, I'd just say ship it.
>
> Reviewed-by: Gregory Price (Meta) <gourry@gourry.net>
Thanks, I'll wait a bit longer for feedback, especially from Hugh and Baolin;
maybe they have some examples where we would actually end up using way more than
1024 disting shared policy ranges even after #1.
--
Cheers,
David
prev parent reply other threads:[~2026-11-16 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 21:36 [PATCH 0/2] mm/mempolicy: shared policy limits for tmpfs/shmem/guest_memfd David Hildenbrand (Arm)
2026-11-13 21:36 ` [PATCH 1/2] mm/mempolicy: merge adjacent shared policy ranges David Hildenbrand (Arm)
2026-11-13 22:23 ` Joshua Hahn
2026-11-14 17:22 ` Gregory Price (Meta)
2026-11-16 16:49 ` Zi Yan
2026-11-13 21:36 ` [PATCH 2/2] mm/mempolicy: limit shared policy ranges per inode David Hildenbrand (Arm)
2026-11-14 17:41 ` Gregory Price (Meta)
2026-11-14 20:16 ` David Hildenbrand (Arm)
2026-11-14 20:25 ` Gregory Price (Meta)
2026-11-15 16:40 ` David Hildenbrand (Arm)
2026-11-16 16:13 ` Gregory Price (Meta)
2026-11-16 22:17 ` David Hildenbrand (Arm) [this message]
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=8e63a932-ede9-4751-9181-5ae25815ce0e@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=corbet@lwn.net \
--cc=gourry@gourry.net \
--cc=hughd@google.com \
--cc=joshua.hahnjy@gmail.com \
--cc=liam@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=rakie.kim@sk.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.com \
/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