From: Jeffle Xu <jefflexu@linux.alibaba.com>
To: vgoyal@redhat.com, stefanha@redhat.com, miklos@szeredi.hu
Cc: virtio-fs@redhat.com, linux-fsdevel@vger.kernel.org,
joseph.qi@linux.alibaba.com
Subject: [PATCH v8 3/7] fuse: support per inode DAX in fuse protocol
Date: Thu, 25 Nov 2021 15:05:26 +0800 [thread overview]
Message-ID: <20211125070530.79602-4-jefflexu@linux.alibaba.com> (raw)
In-Reply-To: <20211125070530.79602-1-jefflexu@linux.alibaba.com>
Expand the fuse protocol to support per inode DAX.
FUSE_HAS_INODE_DAX flag is added indicating if fuse server/client
supporting per inode DAX. It can be conveyed in both FUSE_INIT request
and reply.
FUSE_ATTR_DAX flag is added indicating if DAX shall be enabled for
corresponding file. It is conveyed in FUSE_LOOKUP reply.
Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
---
include/uapi/linux/fuse.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h
index a1dc3ee1d17c..63a9a963f4d9 100644
--- a/include/uapi/linux/fuse.h
+++ b/include/uapi/linux/fuse.h
@@ -187,6 +187,7 @@
*
* 7.35
* - add FOPEN_NOFLUSH
+ * - add FUSE_HAS_INODE_DAX, FUSE_ATTR_DAX
*/
#ifndef _LINUX_FUSE_H
@@ -341,6 +342,7 @@ struct fuse_file_lock {
* write/truncate sgid is killed only if file has group
* execute permission. (Same as Linux VFS behavior).
* FUSE_SETXATTR_EXT: Server supports extended struct fuse_setxattr_in
+ * FUSE_HAS_INODE_DAX: use per inode DAX
*/
#define FUSE_ASYNC_READ (1 << 0)
#define FUSE_POSIX_LOCKS (1 << 1)
@@ -372,6 +374,7 @@ struct fuse_file_lock {
#define FUSE_SUBMOUNTS (1 << 27)
#define FUSE_HANDLE_KILLPRIV_V2 (1 << 28)
#define FUSE_SETXATTR_EXT (1 << 29)
+#define FUSE_HAS_INODE_DAX (1 << 30)
/**
* CUSE INIT request/reply flags
@@ -454,8 +457,10 @@ struct fuse_file_lock {
* fuse_attr flags
*
* FUSE_ATTR_SUBMOUNT: Object is a submount root
+ * FUSE_ATTR_DAX: Enable DAX for this file in per inode DAX mode
*/
#define FUSE_ATTR_SUBMOUNT (1 << 0)
+#define FUSE_ATTR_DAX (1 << 1)
/**
* Open flags
--
2.27.0
next prev parent reply other threads:[~2021-11-25 7:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 7:05 [PATCH v8 0/7] fuse,virtiofs: support per-file DAX Jeffle Xu
2021-11-25 7:05 ` [PATCH v8 1/7] fuse: add fuse_should_enable_dax() helper Jeffle Xu
2021-12-13 18:08 ` Vivek Goyal
2021-11-25 7:05 ` [PATCH v8 2/7] fuse: make DAX mount option a tri-state Jeffle Xu
2021-12-13 18:09 ` Vivek Goyal
2021-11-25 7:05 ` Jeffle Xu [this message]
2021-12-13 18:09 ` [PATCH v8 3/7] fuse: support per inode DAX in fuse protocol Vivek Goyal
2021-11-25 7:05 ` [PATCH v8 4/7] fuse: enable per inode DAX Jeffle Xu
2021-12-13 18:10 ` Vivek Goyal
2021-11-25 7:05 ` [PATCH v8 5/7] fuse: negotiate per inode DAX in FUSE_INIT Jeffle Xu
2021-12-13 18:10 ` Vivek Goyal
2021-11-25 7:05 ` [PATCH v8 6/7] fuse: mark inode DONT_CACHE when per inode DAX hint changes Jeffle Xu
2021-12-07 16:00 ` Vivek Goyal
2021-12-08 1:36 ` JeffleXu
2021-12-13 18:10 ` Vivek Goyal
2021-11-25 7:05 ` [PATCH v8 7/7] Documentation/filesystem/dax: DAX on virtiofs Jeffle Xu
2021-12-13 18:11 ` Vivek Goyal
2021-12-13 18:12 ` [PATCH v8 0/7] fuse,virtiofs: support per-file DAX Vivek Goyal
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=20211125070530.79602-4-jefflexu@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stefanha@redhat.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@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 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).