On Wed, Aug 21, 2024 at 8:04 AM Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>
> On Wed, 21 Aug 2024 at 16:44, Bernd Schubert <bernd.schubert@xxxxxxxxxxx> wrote:
>
> > struct atomic_open
> > {
> > uint64_t atomic_open_flags;
> > struct fuse_open_out open_out;
> > uint8_t future_padding1[16];
> > struct fuse_entry_out entry_out;
> > uint8_t future_padding2[16];
> > }
> >
> >
> > What do you think?
>
> I'm wondering if something like the "compound procedure" in NFSv4
> would work for fuse as well?
Are compound requests still something that's planned to be added to
fuse given that fuse now has support for sending requests over uring,
which diminishes the overhead of kernel/userspace context switches for
sending multiple requests vs 1 big compound request?
The reason I ask is because the mitigation for the stale attributes
data corruption for servers backed by network filesystems we saw in
[1] is dependent on this patch / compound requests. If compound
requests are no longer useful / planned, then what are your thoughts
on [1] as an acceptable solution?
Thanks,
Joanne
[1] https://lore.kernel.org/linux-fsdevel/20240813212149.1909627-1-joannelkoong@xxxxxxxxx/
>
> Thanks,
> Miklos
