[fuse-devel] FUSE kernel module blocking/non-blocking

[Gal R. <GA...@il...>]

Hi all,

By reading the code I notice that all syscalls except release at the end
put the FUSE request by fuse_request_send() routine, which is blocking and
waiting for response.
Even async read/write are at the end reading/writing pages using
fuse_request_send() and not by using fuse_request_send_background().
If this is the case what is the point of implementing asynchronous
operations using the low level API, if at the end the client process is
waiting on a waitq in FUSE device ?

Thanks,
Gal.