MD: improve raid1/10 write performance for fast storage
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest3 patches 9 repliesIn review
- v23 patches 0 repliesSuperseded
- v14 patches 9 repliesSuperseded
Changes in v3 from the cover letter
rebase to latest tree and fix cpuhotplug issue
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | MD: add a specific workqueue to do dispatchdrivers/ drivers/ | +15 | 0 replies | |
| 2/3 | raid1: percpu dispatch for write request if bitmap supporteddrivers/ drivers/ | +88 | 0 replies | |
| 3/3 | raid10: percpu dispatch for write request if bitmap supporteddrivers/ drivers/ | +89 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [patch 0/3 v3] MD: improve raid1/10 write performance for fast storage
In raid1/10, all write requests are dispatched in a single thread. In fast storage, the thread is a bottleneck, because it dispatches request too slow. Also the thread migrates freely, which makes request completion cpu not match with submission cpu even driver/block layer has such capability. This will cause bad cache issue. Both these are not a big deal for slow storage.
Switching the dispatching to percpu/perthread based dramatically increases performance. The more raid disk number is, the more performance boosts. In a 4-disk raid10 setup, this can double the throughput.
percpu/perthread based dispatch doesn't harm slow storage. This is the way how raw device is accessed, and there is correct block plug set which can help do request merge and reduce lock contention.
V2->V3:
rebase to latest tree and fix cpuhotplug issue
V1->V2:
1. droped direct dispatch patches. That has better performance imporvement, but is hopelessly made correct.
2. Add a MD specific workqueue to do percpu dispatch.