Skip to content

Cache async read/write and regular file state

Jens Axboe io-uring 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2io_uring: don't check for io_uring_fops for fixed filesfs/io_uring.c+4 -20 replies
2/2io_uring: cache async and regular file state for fixed filesfs/io_uring.c+64 -120 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

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