From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH REPOST 0/3] rbd: no need for file mapping calculation
Date: Wed, 16 Jan 2013 18:34:54 -0800 [thread overview]
Message-ID: <50F7634E.9010204@inktank.com> (raw)
In-Reply-To: <50E6EC84.2060304@inktank.com>
On 01/04/2013 06:51 AM, Alex Elder wrote:
> Currently every osd request submitted by the rbd code undergoes a
> file mapping operation, which is common with what the ceph file system
> uses. But some analysis shows that there is no need to do this for
> rbd, because it already takes care of its own blocking of image data
> into distinct objects. Removing this simplifies things. I especially
> think removing this improves things conceptually, removing a complex
> mapping operation from the I/O path.
>
> -Alex
>
> [PATCH REPOST 1/3] rbd: pull in ceph_calc_raw_layout()
> [PATCH REPOST 2/3] rbd: open code rbd_calc_raw_layout()
> [PATCH REPOST 3/3] rbd: don't bother calculating file mapping
We'll want to use similar methods later for fancier rbd striping with
format 2 images, but that'll take more restructuring later anyway.
This is fine for now.
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
prev parent reply other threads:[~2013-01-17 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:51 [PATCH REPOST 0/3] rbd: no need for file mapping calculation Alex Elder
2013-01-04 14:52 ` [PATCH REPOST 1/3] rbd: pull in ceph_calc_raw_layout() Alex Elder
2013-01-04 14:53 ` [PATCH REPOST 2/3] rbd: open code rbd_calc_raw_layout() Alex Elder
2013-01-04 14:53 ` [PATCH REPOST 3/3] rbd: don't bother calculating file mapping Alex Elder
2013-01-17 2:34 ` Josh Durgin [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=50F7634E.9010204@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.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