From: Yafang Shao <laoar.shao@gmail.com>
To: akpm@linux-foundation.org, mhocko@suse.com, linux.bhar@gmail.com
Cc: linux-mm@kvack.org, shaoyafang@didiglobal.com,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH v4 0/3] mm: improvements in shrink slab
Date: Thu, 6 Jun 2019 18:14:37 +0800 [thread overview]
Message-ID: <1559816080-26405-1-git-send-email-laoar.shao@gmail.com> (raw)
In the past few days, I found an issue in shrink slab.
We I was trying to fix it, I find there are something in shrink slab need
to be improved.
- #1 is to expose the min_slab_pages to help us analyze shrink slab.
- #2 is an code improvement.
- #3 is a fix to a issue. This issue is very easy to produce.
In the zone reclaim mode.
First you continuously cat a random non-exist file to produce
more and more dentry, then you read big file to produce page cache.
Finally you will find that the denty will never be shrunk.
In order to fix this issue, a new bitmask no_pagecache is introduce,
which is 0 by defalt.
Changes since v3:
A new bitmask no_pagecache is introduced in struct scan_control.
Yafang Shao (3):
mm/vmstat: expose min_slab_pages in /proc/zoneinfo
mm/vmscan: change return type of shrink_node() to void
mm/vmscan: shrink slab in node reclaim
mm/vmscan.c | 33 +++++++++++++++++++++++++++++----
mm/vmstat.c | 8 ++++++++
2 files changed, 37 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-06-06 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 10:14 Yafang Shao [this message]
2019-06-06 10:14 ` [PATCH v4 1/3] mm/vmstat: expose min_slab_pages in /proc/zoneinfo Yafang Shao
2019-06-06 10:14 ` [PATCH v4 2/3] mm/vmscan: change return type of shrink_node() to void Yafang Shao
2019-06-06 10:14 ` [PATCH v4 3/3] mm/vmscan: shrink slab in node reclaim Yafang Shao
2019-06-06 11:17 ` [PATCH v4 0/3] mm: improvements in shrink slab Michal Hocko
2019-06-06 14:18 ` Yafang Shao
2019-06-06 14:44 ` Michal Hocko
2019-06-06 15:03 ` Yafang Shao
2019-06-06 15:33 ` 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=1559816080-26405-1-git-send-email-laoar.shao@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;
as well as URLs for NNTP newsgroup(s).