From: Hao Xu <hao.xu@linux.dev>
To: "fuse-devel@lists.sourceforge.net"
<fuse-devel@lists.sourceforge.net>,
miklos@szeredi.hu
Cc: Antonio SJ Musumeci <trapexit@spawn.link>,
linux-fsdevel@vger.kernel.org,
Bernd Schubert <bernd.schubert@fastmail.fm>
Subject: [RFC] FUSE: add another flag to support shared mmap in FOPEN_DIRECT_IO mode
Date: Tue, 2 May 2023 15:28:50 +0800 [thread overview]
Message-ID: <5683716d-9b1d-83d6-9dd1-a7ad3d05cbb1@linux.dev> (raw)
Hi all,
From discussion with Bernd, I get that FOPEN_DIRECT_IO is designed for
those user cases where users want strong coherency like network
filesystems, where one server serves multiple remote clients. And thus
shared mmap is disabled since local page cache existence breaks this
kind of coherency.
But here our use case is one virtiofs daemon serve one guest vm, We use
FOPEN_DIRECT_IO to reduce memory footprint not for coherency. So we
expect shared mmap works in this case. Here I suggest/am implementing
adding another flag to indicate this kind of cases----use
FOPEN_DIRECT_IO not for coherency----so that shared mmap works.
Thanks,
Hao
next reply other threads:[~2023-05-02 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 7:28 Hao Xu [this message]
2023-05-02 7:37 ` [RFC] FUSE: add another flag to support shared mmap in FOPEN_DIRECT_IO mode Bernd Schubert
2023-05-03 5:09 ` Hao Xu
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=5683716d-9b1d-83d6-9dd1-a7ad3d05cbb1@linux.dev \
--to=hao.xu@linux.dev \
--cc=bernd.schubert@fastmail.fm \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=trapexit@spawn.link \
/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).