From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH 0/4] rbd: disavow any support for multiple osd ops
Date: Wed, 14 Nov 2012 10:33:20 -0600 [thread overview]
Message-ID: <50A3C7D0.2050809@inktank.com> (raw)
The rbd code is rife with places where it seems that an
osd request could support multiple osd ops. But the
reality is that there are spots in rbd as well as libceph
and the messenger that make such support impossible without
some (upcoming, planned) additional work.
This series starts by getting rid of the notion that
anything but a single op will be passed for an osd
operation. The first two patches just make it clear
that we never actually do send more than one op from
rbd anyway, the last two make the code reflect that,
simplifying things in the process.
-Alex
[PATCH 1/4] rbd: pass num_op with ops array
[PATCH 2/4] libceph: pass num_op with ops
[PATCH 3/4] rbd: there is really only one op
[PATCH 4/4] rbd: assume single op in a request
next reply other threads:[~2012-11-14 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 16:33 Alex Elder [this message]
2012-11-14 16:34 ` [PATCH 1/4] rbd: pass num_op with ops array Alex Elder
2012-11-14 16:34 ` [PATCH 2/4] libceph: pass num_op with ops Alex Elder
2012-11-14 16:34 ` [PATCH 3/4] rbd: there is really only one op Alex Elder
2012-11-14 16:35 ` [PATCH 4/4] rbd: assume single op in a request Alex Elder
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=50A3C7D0.2050809@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.