From: Yu Zhao <yuzhao@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Yu Zhao <yuzhao@google.com>
Subject: [PATCH mm-unstable v1 0/6] mm/mglru: performance optimizations
Date: Sun, 1 Dec 2024 20:28:17 -0700 [thread overview]
Message-ID: <20241202032823.2741019-1-yuzhao@google.com> (raw)
This series improves performance for some previously discussed test
cases. Most of the code changes gathered here has been floating on the
mailing list [1][2]. They are now properly organized and have gone
through various benchmarks on both client and server devices,
including Android, FIO, memcached, multiple VMs and MongoDB.
[1] https://lore.kernel.org/CAOUHufahuWcKf5f1Sg3emnqX+cODuR=2TQo7T4Gr-QYLujn4RA@mail.gmail.com/
[2] https://lore.kernel.org/CAOUHufawNerxqLm7L9Yywp3HJFiYVrYO26ePUb1jH-qxNGWzyA@mail.gmail.com/
Yu Zhao (6):
mm/mglru: clean up workingset
mm/mglru: optimize deactivation
mm/mglru: rework aging feedback
mm/mglru: rework type selection
mm/mglru: rework refault detection
mm/mglru: rework workingset protection
include/linux/mm_inline.h | 94 +++++----
include/linux/mmzone.h | 88 +++++---
mm/swap.c | 65 ++++--
mm/vmscan.c | 423 +++++++++++++++++---------------------
mm/workingset.c | 69 +++----
5 files changed, 374 insertions(+), 365 deletions(-)
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-12-02 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 3:28 Yu Zhao [this message]
2024-12-02 3:28 ` [PATCH mm-unstable v1 1/6] mm/mglru: clean up workingset Yu Zhao
2024-12-02 3:28 ` [PATCH mm-unstable v1 2/6] mm/mglru: optimize deactivation Yu Zhao
2024-12-02 3:28 ` [PATCH mm-unstable v1 3/6] mm/mglru: rework aging feedback Yu Zhao
2024-12-02 3:28 ` [PATCH mm-unstable v1 4/6] mm/mglru: rework type selection Yu Zhao
2024-12-02 3:28 ` [PATCH mm-unstable v1 5/6] mm/mglru: rework refault detection Yu Zhao
2024-12-02 3:28 ` [PATCH mm-unstable v1 6/6] mm/mglru: rework workingset protection Yu Zhao
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=20241202032823.2741019-1-yuzhao@google.com \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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