io-wq fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | io-wq: fix queue stalling racefs/ | +7 | 0 replies | |
| 2/5 | io-wq: split bounded and unbounded work into separate listsfs/ | +68 | 0 replies | |
| 3/5 | io-wq: only exit on fatal signalsfs/ | +3 | 0 replies | |
| 4/5 | io-wq: get rid of FIXED worker flagfs/ | +16 | 0 replies | |
| 5/5 | io-wq: make worker creation resilient against signalsfs/ | +166 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCHSET 0/5] io-wq fixes
Hi,
Got a report on io-wq stalls, and it turned into quite the rabbit hole of fixes. There are two main things fixed by this series:
1) Single ring that has a lot of bounded vs unbounded traffic. The fix is mainly just splitting the bounded and unbounded lists, so that we never stall bounded unnecessarily. There are further cleanups possible on top of this, but that should be deferred to 5.16.
2) Workloads that have io-wq work and rely heavily on signaling to communicate between processes/threads. This can interfere with worker creation, and this is particularly troublesome if it just happens to occur with the first worker creation.
In general, harden the worker creation and ensure we handle failures in terms of allocations and worker creations.
Signature · 1 line
Jens Axboe