From: Tal Zussman <tz2294@columbia.edu>
To: David Howells <dhowells@redhat.com>
Cc: Ilya Dryomov <idryomov@gmail.com>,
Alex Markuze <amarkuze@redhat.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Christian Brauner <brauner@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Zi Yan <ziy@nvidia.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/10] ceph: convert writeback path to folios
Date: Fri, 9 Oct 2026 20:16:30 -0400 [thread overview]
Message-ID: <35f4d048-c858-471f-bf9f-24a976094f73@columbia.edu> (raw)
In-Reply-To: <1043695.1791475206@warthog.procyon.org.uk>
H
On 10/8/26 12:00 PM, David Howells wrote:
> Hi Tal,
>
> Apologies for not reaching out to you before, but I keep getting diverted on
> to other thing - usually by AI patch reviews.
>
> Just to note that I have patches in the works to convert ceph to use netfslib
> and thus strip out all the dealing with pages/folios as much as possible -
> even getting down into the protocol and replacing the five different page
> carrying types with the same structure as is at the core of netfslib (bvecq
> chains) and pass the bvecq chains all the way into sendmsg() for transmission.
>
> This also lets me remove ceph's use of the PG_private_2 flag which the MM
> people would really like back. That's then replaced - transparently inside of
> netfslib - by setting a special ->private value on folios read from the
> server, marking them dirty and then having writeback write them to the cache.
>
> It's unfortunately stalled on getting some netfslib changes in, though there
> may be hope for making some progress in this merge window.
>
> If you go to my tree here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/
>
> The netfs-next[12345] branches are the prerequisite patches I'm trying to get
> in at the moment, divided into five batches.
>
> On top of that is my netfs-crypt branch that has content crypto support
>
> And then on top of that is my ceph-iter branch. Note that it's not fully
> working as yet and I'm still testing and fixing bits of it.
>
That's great, I see it removes the ceph pagelist and with it the last couple
callers of __page_cache_alloc(). I wasn't planning on sending additional ceph
patches in the near future, as they would all require getting into the
protocol, so it's great to hear you're working on this!
> If you want to push these patches first, I can always adapt my patches to take
> account of them.
>
It'd be great to get this series in sooner rather than later. I think it's
ready to be merged and it would let us remove five page wrappers of folio
functions immediately. Hopefully since it's fairly small it won't cause you
too much trouble.
Thanks,
Tal
prev parent reply other threads:[~2026-10-10 0:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 16:11 Tal Zussman
2026-09-02 16:11 ` [PATCH v5 01/10] ceph: fix error handling when the OSD client is stopping in ceph_submit_write() Tal Zussman
2026-09-02 16:11 ` [PATCH v5 02/10] ceph: wait for pending fscache write in write_folio_nounlock() Tal Zussman
2026-09-02 16:11 ` [PATCH v5 03/10] ceph: add ceph_folio_snap_context() Tal Zussman
2026-09-02 16:11 ` [PATCH v5 04/10] ceph: convert ceph_wait_until_current_writes_complete() to folios Tal Zussman
2026-09-02 16:11 ` [PATCH v5 05/10] ceph: convert get_writepages_data_length() " Tal Zussman
2026-09-02 16:11 ` [PATCH v5 06/10] ceph: convert ceph_submit_write() " Tal Zussman
2026-09-02 16:11 ` [PATCH v5 07/10] ceph: remove page remnants from write_folio_nounlock() Tal Zussman
2026-09-02 16:11 ` [PATCH v5 08/10] ceph: convert page cleanup loop in writepages_finish() to folios Tal Zussman
2026-09-02 16:11 ` [PATCH v5 09/10] ceph: remove ceph_fscrypt_pagecache_page() and ceph_fscrypt_page_offset() Tal Zussman
2026-09-02 16:11 ` [PATCH v5 10/10] ceph: rename ceph_check_page_before_write() to ceph_check_folio_before_write() Tal Zussman
2026-10-08 16:00 ` [PATCH v5 00/10] ceph: convert writeback path to folios David Howells
2026-10-10 0:16 ` Tal Zussman [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=35f4d048-c858-471f-bf9f-24a976094f73@columbia.edu \
--to=tz2294@columbia.edu \
--cc=amarkuze@redhat.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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
all inboxes | Powered by JetHome®