Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <baoquan.he@linux.dev>
To: Christoph Hellwig <hch@lst.de>
Cc: 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: Re: better block swap batching and a different take on swap_ops v2
Date: Mon, 1 Jun 2026 21:29:30 +0800	[thread overview]
Message-ID: <ah2JOjCiDqXvPci_@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260601113449.3464734-1-hch@lst.de>

Hi Christoph,

On 06/01/26 at 01:34pm, Christoph Hellwig wrote:
> 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.

What tree is this series based on? I tried the latest mainline,
linux-next main branch and Andrew's mm-unstable, all failed. 

And by the way, usually we add version number in each patch's subject as
"[PATCH v2] xxx ".

Thanks
Baoquan


  parent reply	other threads:[~2026-06-01 13:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 11:34 better block swap batching and a different take on swap_ops v2 Christoph Hellwig
2026-06-01 11:34 ` [PATCH 1/8] shmem: provide a shmem_write_folio wrapper Christoph Hellwig
2026-06-04  9:43   ` Baoquan He
2026-06-05 17:07   ` Nhat Pham
2026-06-09  8:55   ` better shmem writeback interface for drm, was: " Christoph Hellwig
2026-06-11  3:19   ` Chris Li
2026-06-01 11:34 ` [PATCH 2/8] mm: merge writeout into pageout Christoph Hellwig
2026-06-04  9:44   ` Baoquan He
2026-06-05 17:07   ` Nhat Pham
2026-06-09  8:49   ` 7.2 candidate? was: " Christoph Hellwig
2026-06-09  9:22     ` David Hildenbrand (Arm)
2026-06-10 16:43   ` Johannes Weiner
2026-06-11  3:20   ` Chris Li
2026-06-01 11:34 ` [PATCH 3/8] mm/swap: introduce struct swap_io_ctx Christoph Hellwig
2026-06-04 10:58   ` Baoquan He
2026-06-05 17:41   ` Nhat Pham
2026-06-09  8:43     ` Christoph Hellwig
2026-06-01 11:34 ` [PATCH 4/8] mm/swap: also use struct swap_iocb for block I/O Christoph Hellwig
2026-06-04 10:59   ` Baoquan He
2026-06-04 11:37   ` Baoquan He
2026-06-01 11:34 ` [PATCH 5/8] mm/swap: remove count_swpout_vm_event Christoph Hellwig
2026-06-04 11:37   ` Baoquan He
2026-06-05 17:50   ` Nhat Pham
2026-06-01 11:34 ` [PATCH 6/8] mm/swap: use swap_ops to register swap device's methods Christoph Hellwig
2026-06-05 17:53   ` Nhat Pham
2026-06-01 11:34 ` [PATCH 7/8] mm/swap: remove SWP_FS_OPS Christoph Hellwig
2026-06-05  5:21   ` Baoquan He
2026-06-09  8:45     ` Christoph Hellwig
2026-06-05 17:58   ` Nhat Pham
2026-06-01 11:34 ` [PATCH 8/8] mm/vmstat: add NRSWP{IN,OUT} counters Christoph Hellwig
2026-06-05  7:16   ` Baoquan He
2026-06-09  8:46     ` Christoph Hellwig
2026-06-05 17:48   ` Nhat Pham
2026-06-01 13:29 ` Baoquan He [this message]
2026-06-01 14:50   ` better block swap batching and a different take on swap_ops v2 Christoph Hellwig
2026-06-01 15:17     ` Baoquan He
2026-06-01 15:25       ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2026-06-14 15:52 Jianyue Wu

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=ah2JOjCiDqXvPci_@MiWiFi-R3L-srv \
    --to=baoquan.he@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=chrisl@kernel.org \
    --cc=hch@lst.de \
    --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