CEPH filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: ceph-devel@vger.kernel.org, dhowells@redhat.com
Cc: idryomov@gmail.com, xiubli@redhat.com, linux-cachefs@redhat.com
Subject: [RFC PATCH 0/5] ceph: convert to netfs_direct_read_iter
Date: Thu,  7 Apr 2022 08:02:19 -0400	[thread overview]
Message-ID: <20220407120224.76156-1-jlayton@kernel.org> (raw)

This patch is based on top of David Howells' netfs-lib branch [1]. That
tree adds new O_DIRECT read helpers to netfs.ko. This patchset converts
ceph to use it. With this, all of the usual xfstests pass for me on
ceph.

We should be able to rip out a large part of ceph_direct_read_write with
this set. I haven't done that here, and will probably wait until we have
converted ceph to use netfs DIO write helpers (which don't exist yet).
Once that's in place, we can just remove that function and related
infrastructure wholesale.

I'd like to get this into our testing branch for an eventual merge into
v5.19. We need it in our testing branch for a bit though.

David, in the past, I think we just based our master branch on top of
whatever branch you were feeding to -next. Around -rc3, could you
rebase netfs-lib on top of that and use that as a base for what you're
feeding into -next? Then we can just base our -next feeder branch onto
yours.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-lib

David Howells (1):
  ceph: Use the provided iterator in ceph_netfs_issue_op()

Jeff Layton (4):
  netfs: don't error out on short DIO reads
  ceph: set rsize in netfs_i_context from mount options
  ceph: enhance dout messages in issue_read codepaths
  ceph: switch to netfs_direct_read_iter

 fs/ceph/addr.c  | 55 ++++++++++++++++++++++++++++++++-----------------
 fs/ceph/file.c  |  3 +--
 fs/ceph/inode.c |  3 ++-
 fs/netfs/io.c   |  5 -----
 4 files changed, 39 insertions(+), 27 deletions(-)
-- 
2.35.1


             reply	other threads:[~2022-04-07 12:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 12:02 Jeff Layton [this message]
2022-04-07 12:02 ` [RFC PATCH 1/5] netfs: don't error out on short DIO reads Jeff Layton
2022-04-07 12:02 ` [RFC PATCH 2/5] ceph: set rsize in netfs_i_context from mount options Jeff Layton
2022-04-07 12:02 ` [RFC PATCH 3/5] ceph: Use the provided iterator in ceph_netfs_issue_op() Jeff Layton
2022-04-07 12:02 ` [RFC PATCH 4/5] ceph: enhance dout messages in issue_read codepaths Jeff Layton
2022-04-07 12:02 ` [RFC PATCH 5/5] ceph: switch to netfs_direct_read_iter Jeff Layton

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=20220407120224.76156-1-jlayton@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dhowells@redhat.com \
    --cc=idryomov@gmail.com \
    --cc=linux-cachefs@redhat.com \
    --cc=xiubli@redhat.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