From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/7] rbd: existence check or layered writes
Date: Fri, 19 Apr 2013 20:04:25 -0700 [thread overview]
Message-ID: <517205B9.4090806@inktank.com> (raw)
In-Reply-To: <516CC6E4.6070307@inktank.com>
On 04/15/2013 08:35 PM, Alex Elder wrote:
> I've broken these patches into three groups.
>
> The first two are sort of cleanup from prior patches.
>
> The next one adds support for simple ops that contain
> a single data item, which I've termed "raw data."
>
> The next two are some more refinements but they
> were done intentionally to prepare for the last
> one.
>
> The sixth puts in place flags on object requests
> that allow the last patch to determine whether it
> needs to issue a STAT call for a target object
> before doing a layered write request.
>
> The layered write request ends up being fairly
> simple. Existence flags are recorded for the
> target of object requests. If it is unknown
> whether the object exists, a new standalone
> object request is created to do a STAT on the
> object. The result (success or ENOENT) is
> recorded in a flag in the original request,
> at which point the original request is
> re-submitted.
>
> This is the first step in doing layered writes.
>
> -Alex
>
> [PATCH 1/7] libceph: kill off osd data write_request parameters
> [PATCH 2/7] libceph: clean up osd data field access functions
>
> [PATCH 3/7] libceph: support raw data requests
>
> [PATCH 4/7] rbd: adjust image object request ref counting
> [PATCH 5/7] rbd: always check IMG_DATA flag
>
> [PATCH 6/7] rbd: add target object existence flags
> [PATCH 7/7] rbd: issue stat request before layered write
These look good. Just a couple comments on the last one.
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
prev parent reply other threads:[~2013-04-20 3:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 3:35 [PATCH 0/7] rbd: existence check or layered writes Alex Elder
2013-04-16 3:36 ` [PATCH 1/7] libceph: kill off osd data write_request parameters Alex Elder
2013-04-16 3:37 ` [PATCH 2/7] libceph: clean up osd data field access functions Alex Elder
2013-04-16 3:38 ` [PATCH 3/7] libceph: support raw data requests Alex Elder
2013-04-16 3:38 ` [PATCH 4/7] rbd: adjust image object request ref counting Alex Elder
2013-04-16 3:38 ` [PATCH 5/7] rbd: always check IMG_DATA flag Alex Elder
2013-04-16 3:38 ` [PATCH 6/7] rbd: add target object existence flags Alex Elder
2013-04-16 3:38 ` [PATCH 7/7] rbd: issue stat request before layered write Alex Elder
2013-04-18 12:44 ` [PATCH 7/7, v2] " Alex Elder
2013-04-20 3:03 ` Josh Durgin
2013-04-20 3:04 ` 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=517205B9.4090806@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 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.