From: Christoph Hellwig <hch@lst.de>
Cc: baoquan.he@linux.dev, akpm@linux-foundation.org,
chrisl@kernel.org, usama.arif@linux.dev, kasong@tencent.com,
nphamcs@gmail.com, shikemeng@huaweicloud.com,
youngjun.park@lge.com, linux-mm@kvack.org
Subject: better block swap batching and a different take on swap_ops v3
Date: Mon, 6 Jul 2026 11:29:24 +0200 [thread overview]
Message-ID: <20260706092933.766071-1-hch@lst.de> (raw)
Hi all,
this series makes use of the swap_iocb for block as well so that it
doesn't do inefficient single-bio I/O, and then rebases the swap_ops from
Baoquan on top of the now very different method structure.
When running doing kernels builds, which is a workload that doesn't
really do much THP anonymous memory it still gets 2x clustering for
writeout and 1.2x for reading back swap in. The overall times do
not actually change, though.
Changes since v2:
- rebased to 7.2-rc2
- rename swap_add_page to swap_add_folio
- rename SWAP_OPS_F_NOFS to SWAP_OPS_F_REQUIRE_NOFS and document it
- improve various commit logs
- spelling fixes
Changes since v1:
- drop the memcg accounting for fs backed swap as it can't really
work as-is
- change the related refactoring to not create a bisection hazard or
compile issue with the wrong set of cgroup config options enabled
- remove a now dead function
Diffstat:
Documentation/filesystems/locking.rst | 5
Documentation/filesystems/vfs.rst | 4
drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 2
drivers/gpu/drm/ttm/ttm_backup.c | 2
fs/nfs/file.c | 4
fs/smb/client/file.c | 4
include/linux/shmem_fs.h | 5
include/linux/swap.h | 7
include/linux/vm_event_item.h | 4
mm/madvise.c | 16
mm/page_io.c | 585 ++++++++++++++----------------
mm/shmem.c | 18
mm/swap.h | 67 +--
mm/swap_state.c | 53 +-
mm/swapfile.c | 11
mm/vmscan.c | 30 -
mm/vmstat.c | 6
mm/zswap.c | 4
18 files changed, 431 insertions(+), 396 deletions(-)
next reply other threads:[~2026-07-06 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 9:29 Christoph Hellwig [this message]
2026-07-06 9:29 ` [PATCH 1/7] shmem: provide a shmem_write_folio wrapper Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2026-07-06 13:21 better block swap batching and a different take on swap_ops v3 Christoph Hellwig
2026-07-06 17:21 ` Andrew Morton
2026-07-06 9:28 Christoph Hellwig
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=20260706092933.766071-1-hch@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shikemeng@huaweicloud.com \
--cc=usama.arif@linux.dev \
--cc=youngjun.park@lge.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