From: Johannes Weiner <hannes@cmpxchg.org>
To: Efly Young <yangyifei03@kuaishou.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Michal Hocko <mhocko@suse.com>,
Shakeel Butt <shakeelb@google.com>,
Yosry Ahmed <yosryahmed@google.com>
Subject: Re: [PATCH] mm:vmscan: fix inaccurate reclaim during proactive reclaim
Date: Thu, 20 Jul 2023 12:24:40 -0400 [thread overview]
Message-ID: <20230720162440.GA1015794@cmpxchg.org> (raw)
In-Reply-To: <20230720072708.55067-1-yangyifei03@kuaishou.com>
On Thu, Jul 20, 2023 at 03:27:08PM +0800, Efly Young wrote:
> Before commit f53af4285d77 ("mm: vmscan: fix extreme overreclaim and
> swap floods"), proactive reclaim will extreme overreclaim sometimes.
> But proactive reclaim still inaccurate and some extent overreclaim.
>
> Problematic case is easy to construct. Allocate lots of anonymous
> memory (e.g., 20G) in a memcg, then swapping by writing memory.recalim
> and there is a certain probability of overreclaim. For example, request
> 1G by writing memory.reclaim will eventually reclaim 1.7G or other
> values more than 1G.
>
> The reason is that reclaimer may have already reclaimed part of requested
> memory in one loop, but before adjust sc->nr_to_reclaim in outer loop,
> call shrink_lruvec() again will still follow the current sc->nr_to_reclaim
> to work. It will eventually lead to overreclaim. In theory, the amount
> of reclaimed would be in [request, 2 * request).
>
> Reclaimer usually tends to reclaim more than request. But either direct
> or kswapd reclaim have much smaller nr_to_reclaim targets, so it is
> less noticeable and not have much impact.
>
> Proactive reclaim can usually come in with a larger value, so the error
> is difficult to ignore. Considering proactive reclaim is usually low
> frequency, handle the batching into smaller chunks is a better approach.
>
> Signed-off-by: Efly Young <yangyifei03@kuaishou.com>
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Hey, I didn't write the patch, you did :) Please change it to
Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
You can also add
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
[quoting remainder for new CCs]
> ---
> mm/memcontrol.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 4b27e24..d36cf88 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -6741,8 +6741,8 @@ static ssize_t memory_reclaim(struct kernfs_open_file *of, char *buf,
> lru_add_drain_all();
>
> reclaimed = try_to_free_mem_cgroup_pages(memcg,
> - nr_to_reclaim - nr_reclaimed,
> - GFP_KERNEL, reclaim_options);
> + min(nr_to_reclaim - nr_reclaimed, SWAP_CLUSTER_MAX),
> + GFP_KERNEL, reclaim_options);
>
> if (!reclaimed && !nr_retries--)
> return -EAGAIN;
> --
> 1.8.3.1
next prev parent reply other threads:[~2023-07-20 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 7:27 [PATCH] mm:vmscan: fix inaccurate reclaim during proactive reclaim Efly Young
2023-07-20 16:24 ` Johannes Weiner [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-21 1:41 Efly Young
2023-07-11 9:43 杨逸飞
2023-07-07 10:32 Efly Young
2023-07-07 19:09 ` Andrew Morton
2023-07-11 15:28 ` 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=20230720162440.GA1015794@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeelb@google.com \
--cc=yangyifei03@kuaishou.com \
--cc=yosryahmed@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;
as well as URLs for NNTP newsgroup(s).