From e66b2cfcf4e196ec04c73a33364cb567dbcc5d18 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Thu, 1 Oct 2026 22:59:16 -0300 Subject: 9ns: regular files open with FOPEN_PARALLEL_DIRECT_WRITES, so a write that waits on another write to the same file (an Edit filter writing the ctl its Edit came by) is not queued behind it Linux 6.2 (FUSE 7.38) takes the inode lock shared for such a write unless it appends or goes past the file's end; older kernels ignore the bit. An O_TRUNC open still takes the lock outright, so a second writer that truncates (`>`) still waits; `1<>` does not. Co-Authored-By: Claude Opus 5.5 --- 9ns/src/fuse.zig | 6 ++++++ 1 file changed, 6 insertions(+) (limited to '9ns/src/fuse.zig') diff --git a/9ns/src/fuse.zig b/9ns/src/fuse.zig index e45abc2..5f7b22a 100644 --- a/9ns/src/fuse.zig +++ b/9ns/src/fuse.zig @@ -27,6 +27,12 @@ pub const root_id: u64 = 1; pub const FOPEN_DIRECT_IO: u32 = 1 << 0; pub const FOPEN_KEEP_CACHE: u32 = 1 << 1; pub const FOPEN_NONSEEKABLE: u32 = 1 << 2; +/// Direct writes to one inode go to the server side by side, not one at a +/// time under the inode's lock (protocol 7.38, Linux 6.2; older kernels +/// ignore the bit). A write the server answers only once another write to +/// the same file has run (an Edit whose filter writes the ctl it came by) +/// otherwise waits on itself. +pub const FOPEN_PARALLEL_DIRECT_WRITES: u32 = 1 << 6; pub const FUSE_ASYNC_READ: u32 = 1 << 0; /// The kernel passes O_TRUNC in OPEN instead of a separate SETATTR(size=0); 9P has OTRUNC for exactly this. -- cgit v1.3