From: Hillf Danton <hdanton@sina.com>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: ying.huang@intel.com, hannes@cmpxchg.org, mhocko@suse.com,
mgorman@techsingularity.net, kirill.shutemov@linux.intel.com,
josef@toxicpanda.com, hughd@google.com, shakeelb@google.com,
akpm@linux-foundation.org, hdanton@sina.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [v4 PATCH 1/2] mm: vmscan: remove double slab pressure by inc'ing sc->nr_scanned
Date: Fri, 24 May 2019 12:15:45 +0800 [thread overview]
Message-ID: <20190524041545.10820-1-hdanton@sina.com> (raw)
On Thu, 23 May 2019 10:27:37 +0800 Yang Shi wrote:
> The commit 9092c71bb724 ("mm: use sc->priority for slab shrink targets")
> has broken up the relationship between sc->nr_scanned and slab pressure.
> The sc->nr_scanned can't double slab pressure anymore. So, it sounds no
> sense to still keep sc->nr_scanned inc'ed. Actually, it would prevent
> from adding pressure on slab shrink since excessive sc->nr_scanned would
> prevent from scan->priority raise.
>
The deleted code below wants to get more slab pages shrinked, and it can do
that without raising scan priority first even after commit 9092c71bb724. Or
we may face the risk that priority goes up too much faster than thought, per
the following snippet.
/*
* If we're getting trouble reclaiming, start doing
* writepage even in laptop mode.
*/
if (sc->priority < DEF_PRIORITY - 2)
> The bonnie test doesn't show this would change the behavior of
> slab shrinkers.
>
> w/ w/o
> /sec %CP /sec %CP
> Sequential delete: 3960.6 94.6 3997.6 96.2
> Random delete: 2518 63.8 2561.6 64.6
>
> The slight increase of "/sec" without the patch would be caused by the
> slight increase of CPU usage.
>
> Cc: Josef Bacik <josef@toxicpanda.com>
> Cc: Michal Hocko <mhocko@kernel.org>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com>
> ---
> v4: Added Johannes's ack
>
> mm/vmscan.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 7acd0af..b65bc50 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1137,11 +1137,6 @@ static unsigned long shrink_page_list(struct list_head *page_list,
> if (!sc->may_unmap && page_mapped(page))
> goto keep_locked;
>
> - /* Double the slab pressure for mapped and swapcache pages */
> - if ((page_mapped(page) || PageSwapCache(page)) &&
> - !(PageAnon(page) && !PageSwapBacked(page)))
> - sc->nr_scanned++;
> -
> may_enter_fs = (sc->gfp_mask & __GFP_FS) ||
> (PageSwapCache(page) && (sc->gfp_mask & __GFP_IO));
>
> --
> 1.8.3.1
>
Best Regards
Hillf
next reply other threads:[~2019-05-24 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 4:15 Hillf Danton [this message]
2019-05-24 5:37 ` Yang Shi
-- strict thread matches above, loose matches on Subject: below --
2019-05-23 2:27 Yang Shi
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=20190524041545.10820-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=josef@toxicpanda.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=shakeelb@google.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.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