From: Antonio SJ Musumeci <trapexit@spawn.link>
To: Miklos Szeredi <miklos@szeredi.hu>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
miklos <mszeredi@redhat.com>
Subject: Re: Should FUSE set IO_FLUSHER for the userspace process?
Date: Tue, 25 Oct 2022 11:38:59 -0400 [thread overview]
Message-ID: <7d293f21-c0b4-46eb-6822-4015560f787e@spawn.link> (raw)
In-Reply-To: <CAJfpegv=1UjycheWyANxsoOM5oCf7DGs9OKNzhNw_dSETBDCVQ@mail.gmail.com>
On 9/19/22 05:20, Miklos Szeredi wrote:
> On Sun, 18 Sept 2022 at 13:03, Nikolaus Rath <Nikolaus@rath.org> wrote:
>> Hi,
>>
>> Should the FUSE kernel driver perhaps set PR_SET_IO_FLUSHER for the FUSE
>> userspace process daemon when a connection is opened?
>>
>> If I understand correctly, this is necessary to avoid a deadlocks if the
>> kernel needs to reclaim memory that has to be written back through FUSE.
> The fuse kernel driver is careful to avoid such deadlocks. When
> memory reclaim happens, it copies data to temporary buffers and
> immediately finishes the reclaim from the memory management
> subsystem's point of view. The temp buffers are then sent to
> userspace and written back without having to worry about deadlocks.
> There are lots of details missing from the above description, but this
> is the essence of the writeback deadlock avoidance.
>
> Thanks,
> Miklos
Miklos, does this mean that FUSE servers shouldn't bother setting
PR_SET_IO_FLUSHER? Are there any benefits to setting it explicitly or
detriments to not setting it?
next prev parent reply other threads:[~2022-10-25 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 11:03 Should FUSE set IO_FLUSHER for the userspace process? Nikolaus Rath
2022-09-18 12:52 ` Amir Goldstein
2022-09-19 9:20 ` Miklos Szeredi
2022-10-25 15:38 ` Antonio SJ Musumeci [this message]
2022-10-26 11:58 ` Miklos Szeredi
2022-10-26 12:17 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d293f21-c0b4-46eb-6822-4015560f787e@spawn.link \
--to=trapexit@spawn.link \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.