Cache async read/write and regular file state
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | io_uring: don't check for io_uring_fops for fixed filesfs/ | +4 | 0 replies | |
| 2/2 | io_uring: cache async and regular file state for fixed filesfs/ | +64 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCHSET 5.13 0/2] Cache async read/write and regular file state
Hi,
Patch 1 is just a regular fix/cleanup, there's no need to check for whether or not a file has io_uring fops if it's registered, as we explicitly disallow that at registration time.
Patch 2 uses the bottom 3 (or 2 for 32-bit) bits in the file pointer to cache state that we always use at read/write time. This prevents digging deep into the file, inode, superblock in the fast path.
Signature · 1 line
Jens Axboe