From: Jeff Layton <jlayton@kernel.org>
To: Xiubo Li <xiubli@redhat.com>,
ceph-devel@vger.kernel.org, idryomov@gmail.com
Subject: Re: [PATCH 3/3] ceph: convert to sparse reads
Date: Mon, 14 Mar 2022 08:09:39 -0400 [thread overview]
Message-ID: <d2cd0dd047c40686d2b5e3b64131112a95581a60.camel@kernel.org> (raw)
In-Reply-To: <393b92d5-ce25-92dd-936f-049d7a819d13@redhat.com>
On Mon, 2022-03-14 at 10:22 +0800, Xiubo Li wrote:
> On 3/9/22 8:33 PM, Jeff Layton wrote:
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/ceph/addr.c | 2 +-
> > fs/ceph/file.c | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
> > index 752c421c9922..f42440d7102b 100644
> > --- a/fs/ceph/addr.c
> > +++ b/fs/ceph/addr.c
> > @@ -317,7 +317,7 @@ static void ceph_netfs_issue_op(struct netfs_read_subrequest *subreq)
> > return;
> >
> > req = ceph_osdc_new_request(&fsc->client->osdc, &ci->i_layout, vino, subreq->start, &len,
> > - 0, 1, CEPH_OSD_OP_READ,
> > + 0, 1, CEPH_OSD_OP_SPARSE_READ,
>
> For this possibly should we add one option to disable it ? Just in case
> we need to debug the fscrypt or something else when we hit the
> read/write related issue ?
>
>
Yeah, it's probably a reasonable thing to add. I had that at one point
in development and dropped it. Let me see if I can resurrect that before
I post a v2.
>
> > CEPH_OSD_FLAG_READ | fsc->client->osdc.client->options->read_from_replica,
> > NULL, ci->i_truncate_seq, ci->i_truncate_size, false);
> > if (IS_ERR(req)) {
> > diff --git a/fs/ceph/file.c b/fs/ceph/file.c
> > index feb75eb1cd82..d1956a20c627 100644
> > --- a/fs/ceph/file.c
> > +++ b/fs/ceph/file.c
> > @@ -934,7 +934,7 @@ static ssize_t ceph_sync_read(struct kiocb *iocb, struct iov_iter *to,
> >
> > req = ceph_osdc_new_request(osdc, &ci->i_layout,
> > ci->i_vino, off, &len, 0, 1,
> > - CEPH_OSD_OP_READ, CEPH_OSD_FLAG_READ,
> > + CEPH_OSD_OP_SPARSE_READ, CEPH_OSD_FLAG_READ,
> > NULL, ci->i_truncate_seq,
> > ci->i_truncate_size, false);
> > if (IS_ERR(req)) {
> > @@ -1291,7 +1291,7 @@ ceph_direct_read_write(struct kiocb *iocb, struct iov_iter *iter,
> > vino, pos, &size, 0,
> > 1,
> > write ? CEPH_OSD_OP_WRITE :
> > - CEPH_OSD_OP_READ,
> > + CEPH_OSD_OP_SPARSE_READ,
> > flags, snapc,
> > ci->i_truncate_seq,
> > ci->i_truncate_size,
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2022-03-14 12:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 12:33 [PATCH 0/3] ceph: support for sparse read in msgr2 crc path Jeff Layton
2022-03-09 12:33 ` [PATCH 1/3] libceph: add sparse read support to msgr2 crc state machine Jeff Layton
2022-03-09 13:37 ` Jeff Layton
2022-03-09 12:33 ` [PATCH 2/3] libceph: add sparse read support to OSD client Jeff Layton
2022-03-11 17:08 ` Jeff Layton
2022-03-09 12:33 ` [PATCH 3/3] ceph: convert to sparse reads Jeff Layton
2022-03-14 2:22 ` Xiubo Li
2022-03-14 12:09 ` Jeff Layton [this message]
2022-03-15 6:23 ` [PATCH 0/3] ceph: support for sparse read in msgr2 crc path Xiubo Li
2022-03-15 10:12 ` Jeff Layton
2022-03-15 11:03 ` Xiubo Li
2022-03-15 11:10 ` Jeff Layton
2022-03-15 11:12 ` Xiubo Li
2022-03-15 13:33 ` Jeff Layton
2022-03-16 9:53 ` Xiubo Li
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=d2cd0dd047c40686d2b5e3b64131112a95581a60.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 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.