Enable NO_OFFLOAD support
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | io_uring: grow struct io_kiocb 'flags' to a 64-bit valueinclude/ io_uring/ io_uring/ | +36 | 0 replies | |
| 2/6 | io_uring: move poll_refs up a cacheline to fill a holeinclude/ | +4 | 0 replies | |
| 3/6 | io_uring: add support for NO_OFFLOADinclude/ include/ io_uring/ +2 more | +33 | 0 replies | |
| 4/6 | Revert "io_uring: always go async for unsupported fadvise flags"io_uring/ | +10 | 0 replies | |
| 5/6 | Revert "io_uring: for requests that require async, force it"io_uring/ io_uring/ io_uring/ +4 more | +34 | 0 replies | |
| 6/6 | io_uring: mark opcodes that always need io-wq puntio_uring/ io_uring/ io_uring/ | +23 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCHSET 0/6] Enable NO_OFFLOAD support
Hi,
This series enables support for forcing no-offload for requests that otherwise would have been punted to io-wq. In essence, it bypasses the normal non-blocking issue in favor of just letting the issue block. This is only done for requests that would've otherwise hit io-wq in the offload path, anything pollable will still be doing non-blocking issue. See patch 3 for details.
Patches 1-2 are just prep patches, and patch 4-5 are reverts of async cleanups, and patch 6 enables this for requests that don't support nonblocking issue at all.
Signature · 1 line
Jens Axboe