From: "ying.huang@intel.com" <ying.huang@intel.com>
To: Miaohe Lin <linmiaohe@huawei.com>,
akpm@linux-foundation.org, Christoph Hellwig <hch@infradead.org>
Cc: songmuchun@bytedance.com, hch@infradead.org, willy@infradead.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH v2 7/9] mm/vmscan: take min_slab_pages into account when try to call shrink_node
Date: Tue, 12 Apr 2022 09:36:31 +0800 [thread overview]
Message-ID: <d628e99c1e3b1786a84e6e7a449c1b662c19b7aa.camel@intel.com> (raw)
In-Reply-To: <20220409093500.10329-8-linmiaohe@huawei.com>
On Sat, 2022-04-09 at 17:34 +0800, Miaohe Lin wrote:
> Since commit 6b4f7799c6a5 ("mm: vmscan: invoke slab shrinkers from
> shrink_zone()"), slab reclaim and lru page reclaim are done together
> in the shrink_node. So we should take min_slab_pages into account
> when try to call shrink_node.
>
Looks reasonable to me, copying Johannes.
Hi, Christoph,
Should we check min_unmapped_pages and min_slab_pages in shrink_node()
to avoid reclaim LRU when necessary and vice versa? This may be done
via another 2 scan_control flags.
Best Regards,
Huang, Ying
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/vmscan.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 53f1d0755b34..ba83d8f3e53e 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -4714,7 +4714,8 @@ static int __node_reclaim(struct pglist_data *pgdat, gfp_t gfp_mask, unsigned in
> noreclaim_flag = memalloc_noreclaim_save();
> set_task_reclaim_state(p, &sc.reclaim_state);
>
>
>
>
> - if (node_pagecache_reclaimable(pgdat) > pgdat->min_unmapped_pages) {
> + if (node_pagecache_reclaimable(pgdat) > pgdat->min_unmapped_pages ||
> + node_page_state_pages(pgdat, NR_SLAB_RECLAIMABLE_B) > pgdat->min_slab_pages) {
> /*
> * Free memory by calling shrink node with increasing
> * priorities until we have enough memory freed.
next prev parent reply other threads:[~2022-04-12 1:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 9:34 [PATCH v2 0/9] A few cleanup and fixup patches for vmscan Miaohe Lin
2022-04-09 9:34 ` [PATCH v2 1/9] mm/vmscan: add a comment about MADV_FREE pages check in folio_check_dirty_writeback Miaohe Lin
2022-04-11 11:50 ` ying.huang
2022-04-12 3:07 ` Miaohe Lin
2022-04-11 14:16 ` Christoph Hellwig
2022-04-12 3:15 ` Miaohe Lin
2022-04-12 8:44 ` Oscar Salvador
2022-04-09 9:34 ` [PATCH v2 2/9] mm/vmscan: remove unneeded can_split_huge_page check Miaohe Lin
2022-04-11 14:18 ` Christoph Hellwig
2022-04-12 3:14 ` Miaohe Lin
2022-04-12 0:52 ` ying.huang
2022-04-12 8:59 ` Oscar Salvador
2022-04-12 13:42 ` Miaohe Lin
2022-04-12 14:59 ` David Hildenbrand
2022-04-13 1:26 ` ying.huang
2022-04-13 2:17 ` Miaohe Lin
2022-04-15 3:07 ` ying.huang
2022-04-16 2:34 ` Miaohe Lin
2022-04-09 9:34 ` [PATCH v2 3/9] mm/vmscan: introduce helper function reclaim_page_list() Miaohe Lin
2022-04-09 13:44 ` Matthew Wilcox
2022-04-11 1:53 ` Miaohe Lin
2022-04-11 3:17 ` Matthew Wilcox
2022-04-11 3:26 ` Miaohe Lin
2022-04-09 9:34 ` [PATCH v2 4/9] mm/vmscan: save a bit of stack space in shrink_lruvec Miaohe Lin
2022-04-12 0:57 ` ying.huang
2022-04-12 3:13 ` Miaohe Lin
2022-04-09 9:34 ` [PATCH v2 5/9] mm/vmscan: activate swap-backed executable folios after first usage Miaohe Lin
2022-04-12 0:59 ` ying.huang
2022-04-09 9:34 ` [PATCH v2 6/9] mm/vmscan: take all base pages of THP into account when race with speculative reference Miaohe Lin
2022-04-09 9:34 ` [PATCH v2 7/9] mm/vmscan: take min_slab_pages into account when try to call shrink_node Miaohe Lin
2022-04-12 1:36 ` ying.huang [this message]
2022-04-09 9:34 ` [PATCH v2 8/9] mm/vmscan: remove obsolete comment in kswapd_run Miaohe Lin
2022-04-09 9:35 ` [PATCH v2 9/9] mm/vmscan: use helper folio_is_file_lru() Miaohe Lin
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=d628e99c1e3b1786a84e6e7a449c1b662c19b7aa.camel@intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songmuchun@bytedance.com \
--cc=willy@infradead.org \
/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).