From: "Liam R. Howlett" <Liam.Howlett@oracle.com>
To: Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, zhengtangquan@oppo.com,
Barry Song <v-songbaohua@oppo.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Matthew Wilcox <willy@infradead.org>,
Oscar Salvador <osalvador@suse.de>,
Ryan Roberts <ryan.roberts@arm.com>, Zi Yan <ziy@nvidia.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH RFC v2] mm: add support for dropping LRU recency on process exit
Date: Thu, 22 May 2025 15:07:05 -0400 [thread overview]
Message-ID: <iozdmu4wqtmq5kbd5d3j3f6xim5tsoqwymbdoo3c6v24p2xtej@kiedlpja574i> (raw)
In-Reply-To: <CAGsJ_4yKpRv392rbM=insAPZMA-cwvTNbcPzGAEycfPDzsbJZQ@mail.gmail.com>
* Barry Song <21cnbao@gmail.com> [250521 22:05]:
> Hi Liam,
> I really appreciate your review—thank you!
Thanks.
This came up when discussing another policy type control to an entire
mm [1].
It looks like the consensus is that a new system call for memory
specific controls might be the best way forward, and your requirement
fits well into this idea.
I'd be interested in hearing what you think on this plan.
[1]. https://lore.kernel.org/all/a8aedeb6-2179-4e53-8310-5b81438c2b80@redhat.com/
Regards,
Liam
prev parent reply other threads:[~2025-05-22 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 7:08 Barry Song
2025-05-20 16:19 ` Liam R. Howlett
2025-05-22 2:05 ` Barry Song
2025-05-22 19:07 ` Liam R. Howlett [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=iozdmu4wqtmq5kbd5d3j3f6xim5tsoqwymbdoo3c6v24p2xtej@kiedlpja574i \
--to=liam.howlett@oracle.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=v-songbaohua@oppo.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=zhengtangquan@oppo.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