linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hao Xu <hao.xu@linux.dev>
To: fuse-devel@lists.sourceforge.net, miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org, bernd.schubert@fastmail.fm,
	cgxu519@mykernel.net
Subject: Re: [fuse-devel] [PATCH] fuse: add a new flag to allow shared mmap in FOPEN_DIRECT_IO mode
Date: Tue, 9 May 2023 20:59:06 +0800	[thread overview]
Message-ID: <876d2357-496e-9031-5554-ceeb579f3525@linux.dev> (raw)
In-Reply-To: <20230505081652.43008-1-hao.xu@linux.dev>

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>


Hi Miklos, any comments on this one?


Thanks,

Hao


  parent reply	other threads:[~2023-05-09 12:59 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 ` Hao Xu [this message]
2023-06-08  7:17 ` Hao Xu
2023-06-08 21:28   ` [fuse-devel] " Bernd Schubert
2023-06-09  5:56     ` 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=876d2357-496e-9031-5554-ceeb579f3525@linux.dev \
    --to=hao.xu@linux.dev \
    --cc=bernd.schubert@fastmail.fm \
    --cc=cgxu519@mykernel.net \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).