diff options
author | Amir Goldstein <amir73il@gmail.com> | 2021-10-24 16:26:07 +0300 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2021-10-28 11:20:31 +0300 |
commit | a390ccb316beb8ea594b8695d53926710ca454a3 (patch) | |
tree | 3df484d4fcff192feeb7b182097e8f4b5fa588ac /fs/fuse/virtio_fs.c | |
parent | c6c745b81033a4c1f0e5f3b16398a10f2d000c29 (diff) | |
download | linux-a390ccb316beb8ea594b8695d53926710ca454a3.tar.xz |
fuse: add FOPEN_NOFLUSH
Add flag returned by FUSE_OPEN and FUSE_CREATE requests to avoid flushing
data cache on close.
Different filesystems implement ->flush() is different ways:
- Most disk filesystems do not implement ->flush() at all
- Some network filesystem (e.g. nfs) flush local write cache of
FMODE_WRITE file and send a "flush" command to server
- Some network filesystem (e.g. cifs) flush local write cache of
FMODE_WRITE file without sending an additional command to server
FUSE flushes local write cache of ANY file, even non FMODE_WRITE
and sends a "flush" command to server (if server implements it).
The FUSE implementation of ->flush() seems over agressive and
arbitrary and does not make a lot of sense when writeback caching is
disabled.
Instead of deciding on another arbitrary implementation that makes
sense, leave the choice of per-file flush behavior in the hands of
the server.
Link: https://lore.kernel.org/linux-fsdevel/CAJfpegspE8e6aKd47uZtSYX8Y-1e1FWS0VL0DH2Skb9gQP5RJQ@mail.gmail.com/
Suggested-by: Miklos Szeredi <mszeredi@redhat.com>
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'fs/fuse/virtio_fs.c')
0 files changed, 0 insertions, 0 deletions