RFC fuse: Parallel DIO writes with O_DIRECT
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 6 repliesIn review
v2 from the cover letter
Rebase to 6.5/6.6-fuse-next
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | fuse: DIO writes always use the same code pathfs/ | +9 | 6 replies | |
| 2/2 | libfs: Remove export of direct_write_fallbackfs/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC -next 0/2] fuse: Parallel DIO writes with O_DIRECT
In commit 153524053bbb fuse gained the possibility to do parallel DIO writes, when FOPEN_DIRECT_IO and FOPEN_PARALLEL_DIRECT_WRITES are set. If server side only sets FOPEN_PARALLEL_DIRECT_WRITES, but does not set FOPEN_DIRECT_IO, O_DIRECT from the application is still serialized.
fuse-next has changes in commits b5a2a3a0b776/80e4f25262f9, which allow to take the optimized (in respect to parallel DIO) code path, dirty page flush and page invalidation have to be done unconditionally, though.
v2:
Rebase to 6.5/6.6-fuse-next
Bernd Schubert (2):
[RFC for fuse-next ] fuse: DIO writes always use the same code path
libfs: Remove export of direct_write_fallback
fs/fuse/file.c | 27 +++++++++------------------ fs/libfs.c | 1 - 2 files changed, 9 insertions(+), 19 deletions(-)
Cc Hao Xu <[email protected]>
Cc Christoph Hellwig <[email protected]>
Cc Miklos Szeredi <[email protected]>
Cc Dharmendra Singh <[email protected]>
Signature · 1 line
2.39.2