rbd: improve how rbd ids are selected
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/5 | rbd: encapsulate new rbd id selectiondrivers/ | +19 | 0 replies | |
| 2/5 | rbd: rework calculation of new rbd id'sdrivers/ | +23 | 1 reply | |
| 3/5 | rbd: protect the rbd_dev_list with a spinlockdrivers/ | +0 | 0 replies | |
| 4/5 | rbd: tie rbd_dev_list changes to rbd_id operationsdrivers/ | +21 | 0 replies | |
| 5/5 | rbd: restore previous rbd id sequence behaviordrivers/ | +34 | 2 replies |
Reviews trailers per patch
None of the 5 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Sage Weil |
|---|---|
| Series | R-b |
| 2/5 | |
| 2/5 | |
| 3/5 | |
| 4/5 | |
| 5/5 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/5] rbd: improve how rbd ids are selected
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