From: Yu Zhao <yuzhao@google.com>
To: "T.J. Alumbaugh" <talumbau@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-mm@google.com
Subject: Re: [PATCH mm-unstable v1 0/7] mm: multi-gen LRU: improve
Date: Wed, 25 Jan 2023 14:16:49 -0700 [thread overview]
Message-ID: <CAOUHufYS+wPjgdFsnR0YG=tdTXDdayWFaA-WBVmrbiWsvn1YwQ@mail.gmail.com> (raw)
In-Reply-To: <20230118001827.1040870-1-talumbau@google.com>
On Tue, Jan 17, 2023 at 5:18 PM T.J. Alumbaugh <talumbau@google.com> wrote:
>
> This patch series improves a few MGLRU functions, collects related
> functions, and adds additional documentation.
>
> T.J. Alumbaugh (7):
> mm: multi-gen LRU: section for working set protection
> mm: multi-gen LRU: section for rmap/PT walk feedback
> mm: multi-gen LRU: section for Bloom filters
> mm: multi-gen LRU: section for memcg LRU
> mm: multi-gen LRU: improve lru_gen_exit_memcg()
> mm: multi-gen LRU: improve walk_pmd_range()
> mm: multi-gen LRU: simplify lru_gen_look_around()
>
> Documentation/mm/multigen_lru.rst | 78 ++++-
> include/linux/mm_inline.h | 17 -
> include/linux/mmzone.h | 13 +-
> mm/memcontrol.c | 8 +-
> mm/vmscan.c | 534 ++++++++++++++++--------------
> 5 files changed, 360 insertions(+), 290 deletions(-)
LGTM, thanks.
The design doc is still missing two sections (PID and mm_struct list),
and someone from our team will follow up on that.
prev parent reply other threads:[~2023-01-25 21:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 0:18 T.J. Alumbaugh
2023-01-18 0:18 ` [PATCH mm-unstable v1 1/7] mm: multi-gen LRU: section for working set protection T.J. Alumbaugh
2023-01-18 1:00 ` Matthew Wilcox
2023-01-18 0:18 ` [PATCH mm-unstable v1 2/7] mm: multi-gen LRU: section for rmap/PT walk feedback T.J. Alumbaugh
2023-01-18 0:18 ` [PATCH mm-unstable v1 3/7] mm: multi-gen LRU: section for Bloom filters T.J. Alumbaugh
2023-01-18 0:18 ` [PATCH mm-unstable v1 4/7] mm: multi-gen LRU: section for memcg LRU T.J. Alumbaugh
2023-01-18 0:18 ` [PATCH mm-unstable v1 5/7] mm: multi-gen LRU: improve lru_gen_exit_memcg() T.J. Alumbaugh
2023-01-18 0:18 ` [PATCH mm-unstable v1 6/7] mm: multi-gen LRU: improve walk_pmd_range() T.J. Alumbaugh
2023-01-18 0:18 ` [PATCH mm-unstable v1 7/7] mm: multi-gen LRU: simplify lru_gen_look_around() T.J. Alumbaugh
2023-01-25 21:16 ` Yu Zhao [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='CAOUHufYS+wPjgdFsnR0YG=tdTXDdayWFaA-WBVmrbiWsvn1YwQ@mail.gmail.com' \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@google.com \
--cc=linux-mm@kvack.org \
--cc=talumbau@google.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