From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/6] libceph: send osd requests in tid order
Date: Mon, 25 Mar 2013 21:25:32 -0500 [thread overview]
Message-ID: <5151071C.3000309@inktank.com> (raw)
This series rearranges the way osd requests are placed onto an
osd client's unsent request list so that they are kept in
order based on their transaction ids. The osd expects its
requests from a client to have monotonically increasing tids.
Since requests are sent to the osd in the order they are on
the unsent list if we keep them sorted there this property
is preserved.
-Alex
[PATCH 1/6] libceph: slightly defer registering osd request
[PATCH 2/6] libceph: no more kick_requests() race
[PATCH 3/6] libceph: prepend requests in order when kicking
[PATCH 4/6] libceph: keep request lists in tid order
[PATCH 5/6] libceph: send queued requests when starting new one
[PATCH 6/6] libceph: verify requests queued in order
next reply other threads:[~2013-03-26 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 2:25 Alex Elder [this message]
2013-03-26 2:27 ` [PATCH 1/6] libceph: slightly defer registering osd request Alex Elder
2013-03-26 2:27 ` [PATCH 2/6] libceph: no more kick_requests() race Alex Elder
2013-03-26 2:27 ` [PATCH 3/6] libceph: prepend requests in order when kicking Alex Elder
2013-03-26 14:50 ` [PATCH 3/6, v2] libceph: requeue only sent requests " Alex Elder
2013-03-26 2:27 ` [PATCH 4/6] libceph: keep request lists in tid order Alex Elder
2013-03-26 2:28 ` [PATCH 5/6] libceph: send queued requests when starting new one Alex Elder
2013-03-26 2:28 ` [PATCH 6/6] libceph: verify requests queued in order Alex Elder
2013-03-26 14:50 ` [PATCH 6/6, v2] " Alex Elder
2013-03-26 14:49 ` [PATCH 0/6] libceph: send osd requests in tid order 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=5151071C.3000309@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.