From: slava@dubeyko.com
To: Fan Ni <nifan.cxl@gmail.com>
Cc: David Howells <dhowells@redhat.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 12:00:52 -0700 [thread overview]
Message-ID: <80300ccacebc13ee67100fe256b03f08dfd2819e.camel@dubeyko.com> (raw)
In-Reply-To: <Z9m7wY8dGAlq4z0K@debian>
Hi Fan,
+ CC David Howells <dhowells@redhat.com>
+ CC ceph-devel@vger.kernel.org
On Tue, 2025-03-18 at 11:30 -0700, Fan Ni wrote:
> Hi Viacheslav,
>
> This is Fan Ni. Recently I started to work on some mm work. One thing
> that I am working on is to reduce the use of &folio->page. When I
> check
> the fs/ceph code, I find some code that may be good candidate for the
> work to be done.
>
> I see you sent some patches to add ceph_submit_write(), since the
> change
> I am planning to do is closely related to it, so I reach out to you
> to
> see if you have some input for me.
>
> Based on my reading of the code, it seems ceph_wbc->pages[i] will
> always be the head page of the folio involved. I am thinking maybe we
> can
> keep folios instead of pages here, do you see any reason we should
> not
> use folios here and must be pages?
>
I believe we need to switch from pages to folios in CephFS code. But it
is painful modification. We need to be really careful in this.
As far as I know, David Howells is making significant modification
namely in this direction. I think you need to synchronize the
implementation activity with him. I'd love to be involved but,
currently, I am focused on fixing other issues in CephFS code. :)
Thanks,
Slava.
next parent reply other threads:[~2025-03-18 19:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z9m7wY8dGAlq4z0K@debian>
2025-03-18 19:00 ` slava [this message]
2025-03-18 19:12 ` Question about code in fs/ceph/addr.c Fan Ni
2025-03-18 22:42 ` David Howells
2025-03-18 23:25 ` Fan Ni
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=80300ccacebc13ee67100fe256b03f08dfd2819e.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=nifan.cxl@gmail.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.