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,
Jiachen Zhang <zhangjiachen.jaycee@bytedance.com>,
Wanpeng Li <wanpengli@tencent.com>,
cgxu519@mykernel.net
Subject: [PATCH v4 0/3] fuse: add a new fuse init flag to relax restrictions in no cache mode
Date: Tue, 1 Aug 2023 16:06:44 +0800 [thread overview]
Message-ID: <20230801080647.357381-1-hao.xu@linux.dev> (raw)
From: Hao Xu <howeyxu@tencent.com>
Patch 1 is a fix for private mmap in FOPEN_DIRECT_IO mode
This is added here together since the later two depends on it.
Patch 2 is the main dish
Patch 3 is to maintain direct io logic for shared mmap in FOPEN_DIRECT_IO mode
v3 -> v4
fix race condition for buffered write and direct read by flushing
pages before direct read to avoid to get stale data
v2 -> v3
add patch 1 fix here, and adjust it follow Bernd's comment
add patch 3 which does right thing for shared mmap in FOPEN_DIRECT_IO mode
v1 -> v2:
make the new flag a fuse init one rather than a open flag since it's
not common that different files in a filesystem has different
strategy of shared mmap.
Hao Xu (3):
fuse: invalidate page cache pages before direct write
fuse: add a new fuse init flag to relax restrictions in no cache mode
fuse: write back dirty pages before direct write in direct_io_relax
mode
fs/fuse/file.c | 26 +++++++++++++++++++++++---
fs/fuse/fuse_i.h | 3 +++
fs/fuse/inode.c | 5 ++++-
include/uapi/linux/fuse.h | 4 ++++
4 files changed, 34 insertions(+), 4 deletions(-)
base-commit: 5d0c230f1de8c7515b6567d9afba1f196fb4e2f4
--
2.25.1
next reply other threads:[~2023-08-01 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 8:06 Hao Xu [this message]
2023-08-01 8:06 ` [PATCH 1/3] fuse: invalidate page cache pages before direct write Hao Xu
2023-08-01 10:14 ` Alan Huang
2023-08-01 10:40 ` Hao Xu
2023-08-01 11:04 ` Alan Huang
2023-08-03 4:45 ` Jiachen Zhang
2023-08-01 8:06 ` [PATCH 2/3] fuse: add a new fuse init flag to relax restrictions in no cache mode Hao Xu
2023-08-01 8:06 ` [PATCH 3/3] fuse: write back dirty pages before direct write in direct_io_relax mode Hao Xu
2023-08-03 4:43 ` Jiachen Zhang
2023-08-16 10:29 ` [PATCH v4 0/3] fuse: add a new fuse init flag to relax restrictions in no cache mode 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=20230801080647.357381-1-hao.xu@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 \
--cc=wanpengli@tencent.com \
--cc=zhangjiachen.jaycee@bytedance.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 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).