From: Yafang Shao <laoar.shao@gmail.com>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Mel Gorman <mgorman@techsingularity.net>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] mm/vmscan: calculate reclaimed slab caches in all reclaim paths
Date: Mon, 24 Jun 2019 20:40:46 +0800 [thread overview]
Message-ID: <CALOAHbD9F-ON04uX+Von3EZ113K5ROA239Vo9Eo6dPtMLL1q1w@mail.gmail.com> (raw)
In-Reply-To: <abcc5922-3d58-f9a3-b040-2871d384ab07@virtuozzo.com>
On Mon, Jun 24, 2019 at 8:33 PM Kirill Tkhai <ktkhai@virtuozzo.com> wrote:
>
> On 24.06.2019 15:30, Yafang Shao wrote:
> > On Mon, Jun 24, 2019 at 4:53 PM Kirill Tkhai <ktkhai@virtuozzo.com> wrote:
> >>
> >> On 21.06.2019 13:14, Yafang Shao wrote:
> >>> There're six different reclaim paths by now,
> >>> - kswapd reclaim path
> >>> - node reclaim path
> >>> - hibernate preallocate memory reclaim path
> >>> - direct reclaim path
> >>> - memcg reclaim path
> >>> - memcg softlimit reclaim path
> >>>
> >>> The slab caches reclaimed in these paths are only calculated in the above
> >>> three paths.
> >>>
> >>> There're some drawbacks if we don't calculate the reclaimed slab caches.
> >>> - The sc->nr_reclaimed isn't correct if there're some slab caches
> >>> relcaimed in this path.
> >>> - The slab caches may be reclaimed thoroughly if there're lots of
> >>> reclaimable slab caches and few page caches.
> >>> Let's take an easy example for this case.
> >>> If one memcg is full of slab caches and the limit of it is 512M, in
> >>> other words there're approximately 512M slab caches in this memcg.
> >>> Then the limit of the memcg is reached and the memcg reclaim begins,
> >>> and then in this memcg reclaim path it will continuesly reclaim the
> >>> slab caches until the sc->priority drops to 0.
> >>> After this reclaim stops, you will find there're few slab caches left,
> >>> which is less than 20M in my test case.
> >>> While after this patch applied the number is greater than 300M and
> >>> the sc->priority only drops to 3.
> >>>
> >>> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> >>> ---
> >>> mm/vmscan.c | 7 +++++++
> >>> 1 file changed, 7 insertions(+)
> >>>
> >>> diff --git a/mm/vmscan.c b/mm/vmscan.c
> >>> index 18a66e5..d6c3fc8 100644
> >>> --- a/mm/vmscan.c
> >>> +++ b/mm/vmscan.c
> >>> @@ -3164,11 +3164,13 @@ unsigned long try_to_free_pages(struct zonelist *zonelist, int order,
> >>> if (throttle_direct_reclaim(sc.gfp_mask, zonelist, nodemask))
> >>> return 1;
> >>>
> >>> + current->reclaim_state = &sc.reclaim_state;
> >>> trace_mm_vmscan_direct_reclaim_begin(order, sc.gfp_mask);
> >>>
> >>> nr_reclaimed = do_try_to_free_pages(zonelist, &sc);
> >>>
> >>> trace_mm_vmscan_direct_reclaim_end(nr_reclaimed);
> >>> + current->reclaim_state = NULL;
> >>
> >> Shouldn't we remove reclaim_state assignment from __perform_reclaim() after this?
> >>
> >
> > Oh yes. We should remove it. Thanks for pointing out.
> > I will post a fix soon.
>
> With the change above, feel free to add my Reviewed-by: to all of the series.
>
Sure, thanks for your review.
Thanks
Yafang
prev parent reply other threads:[~2019-06-24 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 10:14 [PATCH 0/2] mm/vmscan: calculate reclaimed slab in all reclaim paths Yafang Shao
2019-06-21 10:14 ` [PATCH 1/2] mm/vmscan: add a new member reclaim_state in struct shrink_control Yafang Shao
2019-06-21 10:14 ` [PATCH 2/2] mm/vmscan: calculate reclaimed slab caches in all reclaim paths Yafang Shao
2019-06-22 3:30 ` Andrew Morton
2019-06-22 6:31 ` Yafang Shao
2019-06-24 8:53 ` Kirill Tkhai
2019-06-24 12:30 ` Yafang Shao
2019-06-24 12:33 ` Kirill Tkhai
2019-06-24 12:40 ` Yafang Shao [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=CALOAHbD9F-ON04uX+Von3EZ113K5ROA239Vo9Eo6dPtMLL1q1w@mail.gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vdavydov.dev@gmail.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).