From: Jeffle Xu <jefflexu@linux.alibaba.com>
To: vgoyal@redhat.com, stefanha@redhat.com, miklos@szeredi.hu
Cc: linux-fsdevel@vger.kernel.org,
virtualization@lists.linux-foundation.org, virtio-fs@redhat.com,
joseph.qi@linux.alibaba.com, bo.liu@linux.alibaba.com
Subject: [virtiofsd PATCH v2 2/4] virtiofsd: expand fuse protocol to support per-file DAX
Date: Wed, 11 Aug 2021 14:56:19 +0800 [thread overview]
Message-ID: <20210811065621.12737-3-jefflexu@linux.alibaba.com> (raw)
In-Reply-To: <20210811065621.12737-1-jefflexu@linux.alibaba.com>
Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
---
include/standard-headers/linux/fuse.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/standard-headers/linux/fuse.h b/include/standard-headers/linux/fuse.h
index 950d7edb7e..7bd006ffcb 100644
--- a/include/standard-headers/linux/fuse.h
+++ b/include/standard-headers/linux/fuse.h
@@ -356,6 +356,7 @@ struct fuse_file_lock {
#define FUSE_MAP_ALIGNMENT (1 << 26)
#define FUSE_SUBMOUNTS (1 << 27)
#define FUSE_HANDLE_KILLPRIV_V2 (1 << 28)
+#define FUSE_PERFILE_DAX (1 << 30)
/**
* CUSE INIT request/reply flags
@@ -440,6 +441,7 @@ struct fuse_file_lock {
* FUSE_ATTR_SUBMOUNT: Object is a submount root
*/
#define FUSE_ATTR_SUBMOUNT (1 << 0)
+#define FUSE_ATTR_DAX (1 << 1)
/**
* Open flags
--
2.27.0
next prev parent reply other threads:[~2021-08-11 6:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 7:06 [PATCH v3 0/8] fuse,virtiofs: support per-file DAX Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 1/8] fuse: add fuse_should_enable_dax() helper Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 2/8] fuse: Make DAX mount option a tri-state Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 3/8] fuse: support per-file DAX Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 4/8] fuse: negotiate if server/client supports " Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 5/8] fuse: enable " Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 6/8] fuse: mark inode DONT_CACHE when per-file DAX indication changes Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 7/8] fuse: support changing per-file DAX flag inside guest Jeffle Xu
2021-08-04 7:06 ` [PATCH v3 8/8] fuse: show '-o dax=inode' option only when FUSE server supports Jeffle Xu
2021-08-04 7:24 ` [PATCH virtiofsd 0/3] virtiofsd: support per-file DAX Jeffle Xu
2021-08-04 7:24 ` [PATCH virtiofsd 1/3] virtiofsd: expand fuse protocol to " Jeffle Xu
2021-08-04 7:24 ` [PATCH virtiofsd 2/3] virtiofsd: support per-file DAX negotiation in FUSE_INIT Jeffle Xu
2021-08-04 7:24 ` [PATCH virtiofsd 3/3] virtiofsd: support per-file DAX in FUSE_LOOKUP Jeffle Xu
2021-08-11 6:56 ` [virtiofsd PATCH v2 0/4] virtiofsd: support per-file DAX Jeffle Xu
2021-08-11 6:56 ` [virtiofsd PATCH v2 1/4] virtiofsd: add .ioctl() support Jeffle Xu
2021-08-11 6:56 ` Jeffle Xu [this message]
2021-08-11 6:56 ` [virtiofsd PATCH v2 3/4] virtiofsd: support per-file DAX negotiation in FUSE_INIT Jeffle Xu
2021-08-11 6:56 ` [virtiofsd PATCH v2 4/4] virtiofsd: support per-file DAX in FUSE_LOOKUP Jeffle Xu
2021-08-11 9:10 ` [virtiofsd PATCH v3 " Jeffle Xu
2021-08-12 2:52 ` [PATCH v3 0/8] fuse,virtiofs: support per-file DAX JeffleXu
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=20210811065621.12737-3-jefflexu@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=bo.liu@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 \
--cc=virtualization@lists.linux-foundation.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).