From: Michal Hocko <mhocko@suse.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>, Yu Zhao <yuzhao@google.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-mm@kvack.org, Yosry Ahmed <yosryahmed@google.com>,
Wei Xu <weixugc@google.com>, Shakeel Butt <shakeelb@google.com>,
Greg Thelen <gthelen@google.com>
Subject: Re: [RFC] Mechanism to induce memory reclaim
Date: Mon, 7 Mar 2022 15:41:45 +0100 [thread overview]
Message-ID: <YiYZqemRVlk2joYn@dhcp22.suse.cz> (raw)
In-Reply-To: <5df21376-7dd1-bf81-8414-32a73cea45dd@google.com>
On Sun 06-03-22 15:11:23, David Rientjes wrote:
[...]
> Some questions to get discussion going:
>
> - Overall feedback or suggestions for the proposal in general?
Do we really need this interface? What would be usecases which cannot
use an existing interfaces we have for that? Most notably memcg and
their high limit?
I do agree that the global means to trigger the reclaim
(min_free_kbytes) is far from a precise tool but it would be interesting
to hear more about why a number of reclaimed pages would be a more
useful interface. Could you elaborate on that please?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-03-07 14:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 23:11 David Rientjes
2022-03-07 0:49 ` Yu Zhao
2022-03-07 14:41 ` Michal Hocko [this message]
2022-03-07 18:31 ` Shakeel Butt
2022-03-07 20:26 ` Johannes Weiner
2022-03-08 12:53 ` Michal Hocko
2022-03-08 14:44 ` Dan Schatzberg
2022-03-08 16:05 ` Michal Hocko
2022-03-08 17:21 ` Wei Xu
2022-03-08 17:23 ` Johannes Weiner
2022-03-08 12:52 ` Michal Hocko
2022-03-09 22:03 ` David Rientjes
2022-03-10 16:58 ` Johannes Weiner
2022-03-10 17:25 ` Shakeel Butt
2022-03-10 17:33 ` Wei Xu
2022-03-10 17:42 ` Johannes Weiner
2022-03-07 20:50 ` Johannes Weiner
2022-03-07 22:53 ` Wei Xu
2022-03-08 12:53 ` Michal Hocko
2022-03-08 14:49 ` Dan Schatzberg
2022-03-08 19:27 ` Johannes Weiner
2022-03-08 22:37 ` Dan Schatzberg
2022-03-09 22:30 ` David Rientjes
2022-03-10 16:10 ` Johannes Weiner
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=YiYZqemRVlk2joYn@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=weixugc@google.com \
--cc=yosryahmed@google.com \
--cc=yuzhao@google.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