From: Alex Elder <elder@dreamhost.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/5] rbd: improve how rbd ids are selected
Date: Tue, 28 Feb 2012 19:38:13 -0800 [thread overview]
Message-ID: <4F4D9DA5.8050101@dreamhost.com> (raw)
New rbd devices are granted a unique identifiers based on how many
devices are already in existence. This series rearranges how that
is done, switching from using a spinlock to using an atomic variable
to select the next rbd id to use. In the process a bit of the code
got a bit more isolated.
-Alex
next reply other threads:[~2012-02-29 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 3:38 Alex Elder [this message]
2012-02-29 3:40 ` [PATCH 2/5] rbd: encapsulate new rbd id selection Alex Elder
2012-02-29 3:40 ` [PATCH 2/5] rbd: rework calculation of new rbd id's Alex Elder
2012-02-29 20:37 ` Yehuda Sadeh Weinraub
2012-02-29 3:40 ` [PATCH 3/5] rbd: protect the rbd_dev_list with a spinlock Alex Elder
2012-02-29 3:40 ` [PATCH 4/5] rbd: tie rbd_dev_list changes to rbd_id operations Alex Elder
2012-02-29 3:40 ` [PATCH 5/5] rbd: restore previous rbd id sequence behavior Alex Elder
2012-02-29 20:53 ` Yehuda Sadeh Weinraub
2012-02-29 21:27 ` Alex Elder
2012-03-02 19:54 ` [PATCH 0/5] rbd: improve how rbd ids are selected Sage Weil
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=4F4D9DA5.8050101@dreamhost.com \
--to=elder@dreamhost.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.