diff options
author | Bernd Schubert <bschubert@ddn.com> | 2023-10-10 13:18:36 +0200 |
---|---|---|
committer | Nikolaus Rath <Nikolaus@rath.org> | 2023-10-11 08:39:11 +0100 |
commit | 063ef8e03ff669579d3a441bece702283b7654e3 (patch) | |
tree | 7dc4b2ba6bae6e4c4de91f16a1e327bfdc901ff0 /example/passthrough.c | |
parent | ef11cf9eace3cf5f529a23899ae850c09aaf64bc (diff) | |
download | libfuse-063ef8e03ff669579d3a441bece702283b7654e3.tar.gz |
Enabled parallel direct IO writes for passthrough examples
All these passthrough examples don't need writes to be serialized.
Actually, most file systems probably handle non serialized parallel
direct writes - the FOPEN_PARALLEL_DIRECT_WRITES flag is just
to avoid a regression for those file system that rely on serialized
DIO writes in fuse kernel. Passthrough file system forward the IO
to another file system, which actually handles that internally -
serialized in fuser kernel is not needed.
Diffstat (limited to 'example/passthrough.c')
-rw-r--r-- | example/passthrough.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/example/passthrough.c b/example/passthrough.c index 5963d58..dd385c5 100644 --- a/example/passthrough.c +++ b/example/passthrough.c @@ -285,6 +285,7 @@ static int xmp_create(const char *path, mode_t mode, return -errno; fi->fh = res; + fi->parallel_direct_writes = 1; return 0; } @@ -297,6 +298,7 @@ static int xmp_open(const char *path, struct fuse_file_info *fi) return -errno; fi->fh = res; + fi->parallel_direct_writes = 1; return 0; } |