From: Miklos Szeredi <miklos@szeredi.hu>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: Hao Xu <hao.xu@linux.dev>,
fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [fuse-devel] [PATCH] fuse: add a new flag to allow shared mmap in FOPEN_DIRECT_IO mode
Date: Fri, 9 Jun 2023 07:56:05 +0200 [thread overview]
Message-ID: <CAJfpegsd5YEZyzisnfiocVCAwxP64=jgSqhJ5-hurzFA0=-0nw@mail.gmail.com> (raw)
In-Reply-To: <09200d9b-20cb-5864-c42f-e08035d07cd9@fastmail.fm>
On Thu, 8 Jun 2023 at 23:29, Bernd Schubert <bernd.schubert@fastmail.fm> wrote:
>
>
>
> On 6/8/23 09:17, Hao Xu wrote:
> > ping...
> >
> > On 5/5/23 16:16, Hao Xu wrote:
> >> From: Hao Xu <howeyxu@tencent.com>
> >>
> >> FOPEN_DIRECT_IO is usually set by fuse daemon to indicate need of strong
> >> coherency, e.g. network filesystems. Thus shared mmap is disabled since
> >> it leverages page cache and may write to it, which may cause
> >> inconsistence. But FOPEN_DIRECT_IO can be used not for coherency but to
> >> reduce memory footprint as well, e.g. reduce guest memory usage with
> >> virtiofs. Therefore, add a new flag FOPEN_DIRECT_IO_SHARED_MMAP to allow
> >> shared mmap for these cases.
> >>
> >> Signed-off-by: Hao Xu <howeyxu@tencent.com>
> >> ---
> >> fs/fuse/file.c | 11 ++++++++---
> >> include/uapi/linux/fuse.h | 2 ++
> >> 2 files changed, 10 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/fs/fuse/file.c b/fs/fuse/file.c
> >> index 89d97f6188e0..655896bdb0d5 100644
> >> --- a/fs/fuse/file.c
> >> +++ b/fs/fuse/file.c
> >> @@ -161,7 +161,8 @@ struct fuse_file *fuse_file_open(struct fuse_mount
> >> *fm, u64 nodeid,
> >> }
> >> if (isdir)
> >> - ff->open_flags &= ~FOPEN_DIRECT_IO;
> >> + ff->open_flags &=
> >> + ~(FOPEN_DIRECT_IO | FOPEN_DIRECT_IO_SHARED_MMAP);
> >> ff->nodeid = nodeid;
> >> @@ -2509,8 +2510,12 @@ static int fuse_file_mmap(struct file *file,
> >> struct vm_area_struct *vma)
> >> return fuse_dax_mmap(file, vma);
> >> if (ff->open_flags & FOPEN_DIRECT_IO) {
> >> - /* Can't provide the coherency needed for MAP_SHARED */
> >> - if (vma->vm_flags & VM_MAYSHARE)
> >> + /* Can't provide the coherency needed for MAP_SHARED.
> >> + * So disable it if FOPEN_DIRECT_IO_SHARED_MMAP is not
> >> + * set, which means we do need strong coherency.
> >> + */
> >> + if (!(ff->open_flags & FOPEN_DIRECT_IO_SHARED_MMAP) &&
> >> + vma->vm_flags & VM_MAYSHARE)
> >> return -ENODEV;
> >> invalidate_inode_pages2(file->f_mapping);
> >> diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h
> >> index 1b9d0dfae72d..003dcf42e8c2 100644
> >> --- a/include/uapi/linux/fuse.h
> >> +++ b/include/uapi/linux/fuse.h
> >> @@ -314,6 +314,7 @@ struct fuse_file_lock {
> >> * FOPEN_STREAM: the file is stream-like (no file position at all)
> >> * FOPEN_NOFLUSH: don't flush data cache on close (unless
> >> FUSE_WRITEBACK_CACHE)
> >> * FOPEN_PARALLEL_DIRECT_WRITES: Allow concurrent direct writes on
> >> the same inode
> >> + * FOPEN_DIRECT_IO_SHARED_MMAP: allow shared mmap when
> >> FOPEN_DIRECT_IO is set
> >> */
> >> #define FOPEN_DIRECT_IO (1 << 0)
> >> #define FOPEN_KEEP_CACHE (1 << 1)
> >> @@ -322,6 +323,7 @@ struct fuse_file_lock {
> >> #define FOPEN_STREAM (1 << 4)
> >> #define FOPEN_NOFLUSH (1 << 5)
> >> #define FOPEN_PARALLEL_DIRECT_WRITES (1 << 6)
> >> +#define FOPEN_DIRECT_IO_SHARED_MMAP (1 << 7)
> >> /**
> >> * INIT request/reply flags
> >
> >
> >
>
> Sorry, currently get distracted by non-fuse work :/
>
> I think see the reply from Miklos on the initial question, which is on
> fuse-devel. Ah, I see you replied to it.
>
> https://sourceforge.net/p/fuse/mailman/message/37849170/
>
>
> I think what Miklos asks for, is to add a new FUSE_INIT reply flag and
> then to set something like fc->dio_shared_mmap. That way it doesn't need
> to be set for each open, but only once in the server init handler.
> @Miklos, please correct me if I'm wrong.
Yes, that's exactly what I suggested.
Thanks,
Miklos
prev parent reply other threads:[~2023-06-09 5:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:16 [PATCH] fuse: add a new flag to allow shared mmap in FOPEN_DIRECT_IO mode Hao Xu
2023-05-05 14:39 ` [fuse-devel] " Bernd Schubert
2023-05-06 5:04 ` Hao Xu
2023-05-06 7:03 ` Hao Xu
2023-06-26 17:59 ` Bernd Schubert
2023-05-05 20:37 ` Vivek Goyal
2023-05-06 5:01 ` Hao Xu
2023-05-08 9:36 ` Hao Xu
2023-06-13 2:56 ` Jingbo Xu
2023-06-13 3:20 ` Hao Xu
2023-06-20 4:07 ` Jingbo Xu
2023-05-09 12:59 ` [fuse-devel] " Hao Xu
2023-06-08 7:17 ` Hao Xu
2023-06-08 21:28 ` [fuse-devel] " Bernd Schubert
2023-06-09 5:56 ` Miklos Szeredi [this message]
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='CAJfpegsd5YEZyzisnfiocVCAwxP64=jgSqhJ5-hurzFA0=-0nw@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=bernd.schubert@fastmail.fm \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hao.xu@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).