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 <howeyxu@xxxxxxxxxxx> Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx> Cc: Miklos Szeredi <miklos@xxxxxxxxxx> Cc: Dharmendra Singh <dsingh@xxxxxxx> Cc: linux-fsdevel@xxxxxxxxxxxxxxx -- 2.39.2
