From: Alex Elder <elder@inktank.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH 0/5] rbd: clean up use of ctl_mutex
Date: Fri, 31 May 2013 20:23:59 -0500 [thread overview]
Message-ID: <51A94D2F.7060103@inktank.com> (raw)
In-Reply-To: <51A94BC0.4080703@inktank.com>
On 05/31/2013 08:17 PM, Alex Elder wrote:
> This series eliminates most uses of the ctl_mutex for locking.
> Its precise purpose was always a little fuzzy to me; with this
> series in place it is now only used to protect looking up
> ceph clients. It also eliminates some lockdep problems
> reported at unmap time.
These patches are available in the "review/rbd-mutex"
branch of the ceph-client git repository.
>
> -Alex
>
> [PATCH 1/5] rbd: set removing flag while holding list lock
> [PATCH 2/5] rbd: protect against concurrent unmaps
> [PATCH 3/5] rbd: don't hold ctl_mutex to get/put device
> [PATCH 4/5] rbd: use rwsem to protect header updates
> [PATCH 5/5] rbd: take a little credit
>
prev parent reply other threads:[~2013-06-01 1:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 1:17 [PATCH 0/5] rbd: clean up use of ctl_mutex Alex Elder
2013-06-01 1:18 ` [PATCH 1/5] rbd: set removing flag while holding list lock Alex Elder
2013-06-07 17:41 ` Josh Durgin
2013-06-01 1:20 ` [PATCH 2/5] rbd: protect against concurrent unmaps Alex Elder
2013-06-07 17:42 ` Josh Durgin
2013-06-01 1:20 ` [PATCH 3/5] rbd: don't hold ctl_mutex to get/put device Alex Elder
2013-06-07 17:44 ` Josh Durgin
2013-06-01 1:20 ` [PATCH 4/5] rbd: use rwsem to protect header updates Alex Elder
2013-06-07 18:25 ` Josh Durgin
2013-06-01 1:20 ` [PATCH 5/5] rbd: take a little credit Alex Elder
2013-06-07 17:48 ` Josh Durgin
2013-06-01 1:23 ` Alex Elder [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=51A94D2F.7060103@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.