From: Fan Ni <nifan.cxl@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Fan Ni <nifan.cxl@gmail.com>,
slava@dubeyko.com, ceph-devel@vger.kernel.org,
Slava.Dubeyko@ibm.com
Subject: Re: Question about code in fs/ceph/addr.c
Date: Tue, 18 Mar 2025 16:25:19 -0700 [thread overview]
Message-ID: <Z9oA3xSwEQgWzZ83@debian> (raw)
In-Reply-To: <2681465.1742337725@warthog.procyon.org.uk>
On Tue, Mar 18, 2025 at 10:42:05PM +0000, David Howells wrote:
> Hi Fan,
>
> My aim is to get rid of all page/folio handling from the main part of the
> filesystem entirely and use netfslib instead. See:
>
> https://lore.kernel.org/linux-fsdevel/20250313233341.1675324-1-dhowells@redhat.com/T/#u
>
> Now, this is a work in progress, but I think I have a decent shot at having it
> ready for the next merge window after the one that should open in about a
> week.
>
> Note that there, struct ceph_snap_context is built around a netfs_group struct
> and attachment to folios is handled by netfslib as much as possible.
>
> My patches can be obtained here:
>
> https://web.git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=ceph-iter
>
> David
>
Hi David,
Thanks for your information.
That is very useful information to me, since I am still slowly ramp-up mm work and lack
of the whole picture of mm development work.
Just to make it more clear to me, so that means all &folio->page and like
will be taken care of with your patches for fs/, right? If so, I will skip fs
and try to work on other sub-system.
Fan
next prev parent reply other threads:[~2025-03-18 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z9m7wY8dGAlq4z0K@debian>
2025-03-18 19:00 ` Question about code in fs/ceph/addr.c slava
2025-03-18 19:12 ` Fan Ni
2025-03-18 22:42 ` David Howells
2025-03-18 23:25 ` Fan Ni [this message]
2025-03-18 23:39 ` slava
2025-03-19 9:02 ` David Howells
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=Z9oA3xSwEQgWzZ83@debian \
--to=nifan.cxl@gmail.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=slava@dubeyko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.