From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH 0/4] rbd: keep reference to lingering object requests
Date: Sat, 26 Jan 2013 14:39:14 -0600 [thread overview]
Message-ID: <51043EF2.4070305@inktank.com> (raw)
This series applies on top of the new rbd request code.
When an osd request is marked to linger the osd client will keep
a copy of the request, and will resubmit it if necessary. If it
gets resubmitted, it will also call the completion routine again,
and because of that we need to make sure the associated object
request structure remains valid. The last patch in this series
ensures that by taking an extra reference for an object request
set to linger.
-Alex
[PATCH 1/4] rbd: unregister linger in watch sync routine
[PATCH 2/4] rbd: track object rather than osd request for watch
[PATCH 3/4] rbd: decrement obj request count when deleting
[PATCH 4/4] rbd: don't drop watch requests on completion
next reply other threads:[~2013-01-26 20:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 20:39 Alex Elder [this message]
2013-01-26 20:40 ` [PATCH 1/4] rbd: unregister linger in watch sync routine Alex Elder
2013-01-30 19:30 ` Josh Durgin
2013-01-26 20:40 ` [PATCH 2/4] rbd: track object rather than osd request for watch Alex Elder
2013-01-30 19:30 ` Josh Durgin
2013-01-26 20:41 ` [PATCH 3/4] rbd: decrement obj request count when deleting Alex Elder
2013-01-30 19:30 ` Josh Durgin
2013-01-26 20:41 ` [PATCH 4/4] rbd: don't drop watch requests on completion Alex Elder
2013-01-30 19:43 ` Josh Durgin
2013-01-30 20:38 ` Alex Elder
2013-01-30 20:39 ` Josh Durgin
2013-01-30 21:54 ` 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=51043EF2.4070305@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.