From: Andre Ramos <acastroramos1987@gmail.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, rostedt@goodmis.org
Subject: Re: [PATCH] mm: add Adaptive Memory Pressure Signaling (AMPRESS)
Date: Mon, 2 Mar 2026 17:28:24 -0300 [thread overview]
Message-ID: <CALXtAv1j_6T-Pa6yML41YoAJUGykMxKjMBtLAVGFD0TOOz7U4A@mail.gmail.com> (raw)
In-Reply-To: <05e134d8-f600-4ee6-9ce5-4b2ef199b075@kernel.org>
On Mon, Mar 02, 2026 at 02:00:00PM +0100, David Hildenbrand wrote:
> Which value does exposing requested_kb really have if there are
> multiply subscribers to notify? Doesn't quite make sense to even
> expose that.
You're right, that's a real design flaw. With N subscribers each
independently acting on requested_kb, the aggregate reclaim is
unbounded. The field would need to be either dropped or replaced
with a hint that scales with subscriber count — neither of which
was thought through here.
> If apps have droppable caches, a better solution might be to use
> something like MAP_DROPPABLE where possible, still leaving the
> kernel in charge of when and how much memory to reclaim.
That's a much cleaner approach. I'll look into MAP_DROPPABLE.
Thank you for the pointer.
André
prev parent reply other threads:[~2026-03-02 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 3:45 Andre Ramos
2026-03-02 8:52 ` David Hildenbrand (Arm)
2026-03-02 11:48 ` Lorenzo Stoakes
2026-03-02 15:11 ` Johannes Weiner
2026-03-02 15:38 ` Andre Ramos
2026-03-02 17:00 ` David Hildenbrand (Arm)
2026-03-02 20:28 ` Andre Ramos [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=CALXtAv1j_6T-Pa6yML41YoAJUGykMxKjMBtLAVGFD0TOOz7U4A@mail.gmail.com \
--to=acastroramos1987@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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