From: 李培锋 <lipeifeng@oppo.com>
To: akpm@linux-foundation.org, david@redhat.com, osalvador@suse.de,
Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
tkjos@google.com, gregkh@google.com, v-songbaohua@oppo.com,
v-songbaohua@oppo.com
Subject: Re: [PATCH 0/2] Support kshrinkd
Date: Tue, 20 Feb 2024 10:09:16 +0800 [thread overview]
Message-ID: <2e4d50aa-7531-7e36-d999-8eb9b5bf3c7c@oppo.com> (raw)
In-Reply-To: <20240219141703.3851-1-lipeifeng@oppo.com>
add experts from Linux and Google.
在 2024/2/19 22:17, lipeifeng@oppo.com 写道:
> From: lipeifeng <lipeifeng@oppo.com>
>
> 'commit 6d4675e60135 ("mm: don't be stuck to rmap lock on reclaim path")'
> The above patch would avoid reclaim path to stuck rmap lock.
> But it would cause some folios in LRU not sorted by aging because
> the contended-folios in rmap_walk would be putbacked to the head of LRU
> during shrink_folio_list even if the folios are very cold.
>
> The patchset setups new kthread:kshrinkd to reclaim the contended-folio
> in rmap_walk when shrink_folio_list, to avoid to break the rules of LRU.
>
> lipeifeng (2):
> mm/rmap: support folio_referenced to control if try_lock in rmap_walk
> mm: support kshrinkd
>
> include/linux/mmzone.h | 6 ++
> include/linux/rmap.h | 5 +-
> include/linux/swap.h | 3 +
> include/linux/vm_event_item.h | 2 +
> mm/memory_hotplug.c | 2 +
> mm/rmap.c | 5 +-
> mm/vmscan.c | 205 ++++++++++++++++++++++++++++++++++++++++--
> mm/vmstat.c | 2 +
> 8 files changed, 221 insertions(+), 9 deletions(-)
>
prev parent reply other threads:[~2024-02-20 2:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:17 lipeifeng
2024-02-19 14:17 ` [PATCH 2/2] mm: support kshrinkd lipeifeng
2024-02-20 2:11 ` 李培锋
2024-02-20 3:19 ` Barry Song
2024-02-19 16:51 ` [PATCH 0/2] Support kshrinkd Matthew Wilcox
2024-02-20 2:04 ` 李培锋
2024-02-20 2:55 ` Matthew Wilcox
2024-02-20 4:14 ` 李培锋
[not found] ` <20240219141703.3851-2-lipeifeng@oppo.com>
2024-02-20 1:42 ` [PATCH 1/2] mm/rmap: support folio_referenced to control if try_lock in rmap_walk 李培锋
2024-02-20 3:01 ` Barry Song
2024-02-20 4:00 ` 李培锋
2024-02-20 7:16 ` Barry Song
2024-02-20 2:09 ` 李培锋 [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=2e4d50aa-7531-7e36-d999-8eb9b5bf3c7c@oppo.com \
--to=lipeifeng@oppo.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=tkjos@google.com \
--cc=v-songbaohua@oppo.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