From: Michal Hocko <mhocko@kernel.org>
To: Zhou Chengming <zhouchengming1@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, vdavydov@virtuozzo.com,
riel@redhat.com, guohanjun@huawei.com
Subject: Re: [PATCH] update sc->nr_reclaimed after each shrink_slab
Date: Fri, 22 Jul 2016 09:49:13 +0200 [thread overview]
Message-ID: <20160722074913.GD794@dhcp22.suse.cz> (raw)
In-Reply-To: <1469159010-5636-1-git-send-email-zhouchengming1@huawei.com>
On Fri 22-07-16 11:43:30, Zhou Chengming wrote:
> In !global_reclaim(sc) case, we should update sc->nr_reclaimed after each
> shrink_slab in the loop. Because we need the correct sc->nr_reclaimed
> value to see if we can break out.
Does this actually change anything? Maybe I am missing something but
try_to_free_mem_cgroup_pages which is the main entry for the memcg
reclaim doesn't set reclaim_state. I don't remember why... Vladimir?
Have you observed any issues and this patch fixes it or this is just
motivated by the code inspection?
> Signed-off-by: Zhou Chengming <zhouchengming1@huawei.com>
> ---
> mm/vmscan.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index c4a2f45..47133c3 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -2405,6 +2405,11 @@ static bool shrink_zone(struct zone *zone, struct scan_control *sc,
> memcg, sc->nr_scanned - scanned,
> lru_pages);
>
> + if (!global_reclaim(sc) && reclaim_state) {
> + sc->nr_reclaimed += reclaim_state->reclaimed_slab;
> + reclaim_state->reclaimed_slab = 0;
> + }
> +
> /* Record the group's reclaim efficiency */
> vmpressure(sc->gfp_mask, memcg, false,
> sc->nr_scanned - scanned,
> --
> 1.7.7
>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-07-22 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 3:43 Zhou Chengming
2016-07-22 7:49 ` Michal Hocko [this message]
2016-07-22 8:12 ` Vladimir Davydov
2016-07-22 8:18 ` Michal Hocko
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=20160722074913.GD794@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=vdavydov@virtuozzo.com \
--cc=zhouchengming1@huawei.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