From: Xiubo Li <xiubli@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Jeff Layton <jlayton@kernel.org>, "Yan, Zheng" <zyan@redhat.com>,
Sage Weil <sage@redhat.com>,
Patrick Donnelly <pdonnell@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [RFC PATCH] ceph: fix the debug message for calc_layout
Date: Mon, 3 Feb 2020 18:46:50 +0800 [thread overview]
Message-ID: <a032d2e1-e463-e4e7-5583-5c71e52edd96@redhat.com> (raw)
In-Reply-To: <CAOi1vP-pGZ1dBhr_EY8t=jas-16T887HTmtyJuVz70roKiYW1A@mail.gmail.com>
On 2020/2/3 18:25, Ilya Dryomov wrote:
> On Mon, Feb 3, 2020 at 5:02 AM <xiubli@redhat.com> wrote:
>> From: Xiubo Li <xiubli@redhat.com>
>>
>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>> ---
>> net/ceph/osd_client.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/net/ceph/osd_client.c b/net/ceph/osd_client.c
>> index 108c9457d629..6afe36ffc1ba 100644
>> --- a/net/ceph/osd_client.c
>> +++ b/net/ceph/osd_client.c
>> @@ -113,10 +113,11 @@ static int calc_layout(struct ceph_file_layout *layout, u64 off, u64 *plen,
>> if (*objlen < orig_len) {
>> *plen = *objlen;
>> dout(" skipping last %llu, final file extent %llu~%llu\n",
>> - orig_len - *plen, off, *plen);
>> + orig_len - *plen, off, off + *plen);
>> }
>>
>> - dout("calc_layout objnum=%llx %llu~%llu\n", *objnum, *objoff, *objlen);
>> + dout("calc_layout objnum=%llx, object extent %llu~%llu\n", *objnum,
>> + *objoff, *objoff + *objlen);
> Hi Xiubo,
>
> offset~length is how extents are printed both on the OSD side and
> elsewhere in the kernel client.
Okay, so my understanding is not correct then.
Thanks.
> Thanks,
>
> Ilya
>
prev parent reply other threads:[~2020-02-03 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 4:01 [RFC PATCH] ceph: fix the debug message for calc_layout xiubli
2020-02-03 10:25 ` Ilya Dryomov
2020-02-03 10:46 ` Xiubo Li [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=a032d2e1-e463-e4e7-5583-5c71e52edd96@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=pdonnell@redhat.com \
--cc=sage@redhat.com \
--cc=zyan@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.