From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH REPOST 0/4] rbd: explicitly support only one osd op
Date: Fri, 04 Jan 2013 08:43:32 -0600 [thread overview]
Message-ID: <50E6EA94.1040001@inktank.com> (raw)
An osd request can be made up of multiple "ops", all of which are
completed (or not) transactionally. There is partial support for
multiple ops in an rbd request in the rbd code, but it's incomplete
and not even supported by the osd client or the messenger right now.
I see three problems with this partial implementation: it gives a
false impression of how things work; it complicates some code in
some cases where it's not necessary; and it may constrain how one
might pursue fully implementing multiple ops in a request to ways
that don't fit well with how we want to do things.
So this series just simplifies things, making it explicit that there
is only one op in an kernel osd client request right now.
-Alex
[PATCH REPOST 1/4] rbd: pass num_op with ops array
[PATCH REPOST 2/4] libceph: pass num_op with ops
[PATCH REPOST 3/4] rbd: there is really only one op
[PATCH REPOST 4/4] rbd: assume single op in a request
next reply other threads:[~2013-01-04 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:43 Alex Elder [this message]
2013-01-04 14:45 ` [PATCH REPOST 1/4] rbd: pass num_op with ops array Alex Elder
2013-01-04 14:45 ` [PATCH REPOST 2/4] libceph: pass num_op with ops Alex Elder
2013-01-04 14:45 ` [PATCH REPOST 3/4] rbd: there is really only one op Alex Elder
2013-01-04 14:45 ` [PATCH REPOST 4/4] rbd: assume single op in a request Alex Elder
2013-01-17 2:27 ` [PATCH REPOST 0/4] rbd: explicitly support only one osd op Josh Durgin
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=50E6EA94.1040001@inktank.com \
--to=elder@inktank.com \
--cc=ceph-devel@vger.kernel.org \
/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.