CEPH filesystem development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: idryomov@gmail.com, xiubli@redhat.com
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] ceph/libceph: add support for sparse reads to msgr2 crc codepath
Date: Tue, 22 Mar 2022 10:20:06 -0400	[thread overview]
Message-ID: <1ab0277a318eb50827b9e9415b2f35d648967e79.camel@kernel.org> (raw)
In-Reply-To: <20220321182618.134202-1-jlayton@kernel.org>

On Mon, 2022-03-21 at 14:26 -0400, Jeff Layton wrote:
> This is a revised version of the sparse read code I posted a week or so
> ago. Sparse read support is required for fscrypt integration work, but
> may be useful on its own.
> 
> The main differences from the v3 set are a couple of small bugfixes, and
> the addition of a new "sparseread" mount option to force the cephfs
> client to use sparse reads. I also renamed the sparse_ext_len field to
> be sparse_ext_cnt (as suggested by Xiubo).
> 
> Ilya, at this point I'm mostly looking for feedback from you. Does this
> approach seem sound? If so, I'll plan to work on implementing the v2-secure
> and v1 codepaths next.
> 
> These patches are currently available in the 'ceph-sparse-read-v4' tag
> in my kernel tree here:
> 
>     https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/
> 
> Jeff Layton (5):
>   libceph: add spinlock around osd->o_requests
>   libceph: define struct ceph_sparse_extent and add some helpers
>   libceph: add sparse read support to msgr2 crc state machine
>   libceph: add sparse read support to OSD client
>   ceph: add new mount option to enable sparse reads
> 
>  fs/ceph/addr.c                  |  18 ++-
>  fs/ceph/file.c                  |  51 ++++++-
>  fs/ceph/super.c                 |  16 +-
>  fs/ceph/super.h                 |   8 +
>  include/linux/ceph/messenger.h  |  29 ++++
>  include/linux/ceph/osd_client.h |  71 ++++++++-
>  net/ceph/messenger.c            |   1 +
>  net/ceph/messenger_v2.c         | 170 +++++++++++++++++++--
>  net/ceph/osd_client.c           | 255 +++++++++++++++++++++++++++++++-
>  9 files changed, 593 insertions(+), 26 deletions(-)
> 

I've pushed this series into a new branch in the ceph tree called
"wip-sparseread", if anyone wants to test it. Note that ms_mode=secure
and ms_mode=legacy settings do not work properly with sparse reads yet.

-- 
Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2022-03-22 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 18:26 [PATCH v4 0/5] ceph/libceph: add support for sparse reads to msgr2 crc codepath Jeff Layton
2022-03-21 18:26 ` [PATCH v4 1/5] libceph: add spinlock around osd->o_requests Jeff Layton
2022-03-21 18:26 ` [PATCH v4 2/5] libceph: define struct ceph_sparse_extent and add some helpers Jeff Layton
2022-03-21 18:26 ` [PATCH v4 3/5] libceph: add sparse read support to msgr2 crc state machine Jeff Layton
2022-03-21 18:26 ` [PATCH v4 4/5] libceph: add sparse read support to OSD client Jeff Layton
2022-03-21 18:26 ` [PATCH v4 5/5] ceph: add new mount option to enable sparse reads Jeff Layton
2022-03-22  7:56 ` [PATCH v4 0/5] ceph/libceph: add support for sparse reads to msgr2 crc codepath Xiubo Li
2022-03-22 14:20 ` Jeff Layton [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=1ab0277a318eb50827b9e9415b2f35d648967e79.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.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