rbd: disavow any support for multiple osd ops
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | rbd: pass num_op with ops arraydrivers/ | +1 | 0 replies | |
| 2/4 | libceph: pass num_op with opsdrivers/ include/ net/ | +5 | 0 replies | |
| 3/4 | rbd: there is really only one opdrivers/ | +1 | 0 replies | |
| 4/4 | rbd: assume single op in a requestdrivers/ | +4 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] rbd: disavow any support for multiple osd ops
The rbd code is rife with places where it seems that an osd request could support multiple osd ops. But the reality is that there are spots in rbd as well as libceph and the messenger that make such support impossible without some (upcoming, planned) additional work.
This series starts by getting rid of the notion that anything but a single op will be passed for an osd operation. The first two patches just make it clear that we never actually do send more than one op from rbd anyway, the last two make the code reflect that, simplifying things in the process.
-Alex
[PATCH 1/4] rbd: pass num_op with ops array [PATCH 2/4] libceph: pass num_op with ops
[PATCH 3/4] rbd: there is really only one op [PATCH 4/4] rbd: assume single op in a request