From: Yafang Shao <laoar.shao@gmail.com>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux MM <linux-mm@kvack.org>,
shaoyafang@didiglobal.com
Subject: Re: [PATCH v3 3/3] mm/vmscan: shrink slab in node reclaim
Date: Sun, 2 Jun 2019 22:25:40 +0800 [thread overview]
Message-ID: <CALOAHbDUdutd8WhoBRyL_o-=J+a5ViOw7-c-WQr5MRxDbO-W+A@mail.gmail.com> (raw)
In-Reply-To: <20190602135852.GA24957@bharath12345-Inspiron-5559>
On Sun, Jun 2, 2019 at 9:58 PM Bharath Vedartham <linux.bhar@gmail.com> wrote:
>
> On Sun, Jun 02, 2019 at 05:23:00PM +0800, Yafang Shao wrote:
> > In the node reclaim, may_shrinkslab is 0 by default,
> > hence shrink_slab will never be performed in it.
> > While shrik_slab should be performed if the relcaimable slab is over
> > min slab limit.
> >
> > If reclaimable pagecache is less than min_unmapped_pages while
> > reclaimable slab is greater than min_slab_pages, we only shrink slab.
> > Otherwise the min_unmapped_pages will be useless under this condition.
> >
> > reclaim_state.reclaimed_slab is to tell us how many pages are
> > reclaimed in shrink slab.
> >
> > This issue is very easy to produce, first you continuously cat a random
> > non-exist file to produce more and more dentry, then you read big file
> > to produce page cache. And finally you will find that the denty will
> > never be shrunk.
> >
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > ---
> > mm/vmscan.c | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
> >
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index e0c5669..d52014f 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -4157,6 +4157,8 @@ static int __node_reclaim(struct pglist_data *pgdat, gfp_t gfp_mask, unsigned in
> > p->reclaim_state = &reclaim_state;
> >
> > if (node_pagecache_reclaimable(pgdat) > pgdat->min_unmapped_pages) {
> > + sc.may_shrinkslab = (pgdat->min_slab_pages <
> > + node_page_state(pgdat, NR_SLAB_RECLAIMABLE));
> > /*
> > * Free memory by calling shrink node with increasing
> > * priorities until we have enough memory freed.
> > @@ -4164,6 +4166,28 @@ static int __node_reclaim(struct pglist_data *pgdat, gfp_t gfp_mask, unsigned in
> > do {
> > shrink_node(pgdat, &sc);
> > } while (sc.nr_reclaimed < nr_pages && --sc.priority >= 0);
> > + } else {
> > + /*
> > + * If the reclaimable pagecache is not greater than
> > + * min_unmapped_pages, only reclaim the slab.
> > + */
> > + struct mem_cgroup *memcg;
> > + struct mem_cgroup_reclaim_cookie reclaim = {
> > + .pgdat = pgdat,
> > + };
> > +
> > + do {
> > + reclaim.priority = sc.priority;
> > + memcg = mem_cgroup_iter(NULL, NULL, &reclaim);
> > + do {
> > + shrink_slab(sc.gfp_mask, pgdat->node_id,
> > + memcg, sc.priority);
> > + } while ((memcg = mem_cgroup_iter(NULL, memcg,
> > + &reclaim)));
> > +
> > + sc.nr_reclaimed += reclaim_state.reclaimed_slab;
> > + reclaim_state.reclaimed_slab = 0;
> > + } while (sc.nr_reclaimed < nr_pages && --sc.priority >= 0);
> > }
> >
> > p->reclaim_state = NULL;
> > --
> > 1.8.3.1
> >
>
> Hi Yafang,
>
> Just a few questions regarding this patch.
>
> Don't you want to check if the number of slab reclaimable pages is
> greater than pgdat->min_slab_pages before reclaiming from slab in your
> else statement? Where is the check to see whether number of
> reclaimable slab pages is greater than pgdat->min_slab_pages? It looks like your
> shrinking slab on the condition if (node_pagecache_reclaimable(pgdata) >
> min_unmapped_pages) is false, Not if (pgdat->min_slab_pages <
> node_page_state(pgdat, NR_SLAB_RECLAIMABLE))? What do you think?
>
Hi Bharath,
Because in __node_reclaim(), if node_pagecache_reclaimable(pgdat) is
not greater than
pgdat->min_unmapped_pages, then reclaimable slab pages must be greater than
pgdat->min_slab_pages, so we don't need to check it again.
Pls. see the code in node_reclaim():
node_reclaim
if (node_pagecache_reclaimable(pgdat) <= pgdat->min_unmapped_pages &&
node_page_state(pgdat, NR_SLAB_RECLAIMABLE) <= pgdat->min_slab_pages)
return NODE_RECLAIM_FULL;
__node_reclaim();
> Also would it be better if we update sc.may_shrinkslab outside the if
> statement of checking min_unmapped_pages? I think it may look better?
>
> Would it be better if we move updating sc.may_shrinkslab outside the
> if statement where we check min_unmapped_pages and add a else if
> (sc.may_shrinkslab) rather than an else and then start shrinking the slab?
>
Because sc.may_shrinkslab is used in shrink_node() only, while it will not be
used in the else statement, so we don't need to update sc.may_shrinkslab outside
the if statement.
Hope it could clarify.
Feel free to ask me it you still have any questions.
Thanks
Yafang
prev parent reply other threads:[~2019-06-02 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 9:22 [PATCH v3 0/3] mm: improvement in shrink slab Yafang Shao
2019-06-02 9:22 ` [PATCH v3 1/3] mm/vmstat: expose min_slab_pages in /proc/zoneinfo Yafang Shao
2019-06-02 9:22 ` [PATCH v3 2/3] mm/vmscan: change return type of shrink_node() to void Yafang Shao
2019-06-02 9:23 ` [PATCH v3 3/3] mm/vmscan: shrink slab in node reclaim Yafang Shao
2019-06-02 13:58 ` Bharath Vedartham
2019-06-02 14:25 ` 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='CALOAHbDUdutd8WhoBRyL_o-=J+a5ViOw7-c-WQr5MRxDbO-W+A@mail.gmail.com' \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=linux.bhar@gmail.com \
--cc=mhocko@suse.com \
--cc=shaoyafang@didiglobal.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