From: Yafang Shao <laoar.shao@gmail.com>
To: akpm@linux-foundation.org, ktkhai@virtuozzo.com, mhocko@suse.com,
hannes@cmpxchg.org, vdavydov.dev@gmail.com,
mgorman@techsingularity.net
Cc: linux-mm@kvack.org, Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH 0/2] mm/vmscan: calculate reclaimed slab in all reclaim paths
Date: Fri, 21 Jun 2019 18:14:44 +0800 [thread overview]
Message-ID: <1561112086-6169-1-git-send-email-laoar.shao@gmail.com> (raw)
This patchset is to fix the issues in doing shrink slab.
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.
The issues are detailed explained in patch #2.
We should calculate the reclaimed slab caches in every reclaim path.
In order to do it, the struct reclaim_state is placed into the
struct shrink_control.
In node reclaim path, there'is another issue about shrinking slab,
which is adressed in another patch[1].
[1] mm/vmscan: shrink slab in node reclaim
https://lore.kernel.org/linux-mm/1559874946-22960-1-git-send-email-laoar.shao@gmail.com/
Yafang Shao (2):
mm/vmscan: add a new member reclaim_state in struct shrink_control
mm/vmscan: calculate reclaimed slab caches in all reclaim paths
mm/vmscan.c | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-06-21 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 10:14 Yafang Shao [this message]
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
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=1561112086-6169-1-git-send-email-laoar.shao@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).