aboutsummaryrefslogtreecommitdiffstats
path: root/include/linux/ceph
diff options
context:
space:
mode:
authorYan, Zheng <zyan@redhat.com>2017-07-24 05:59:39 -0400
committerIlya Dryomov <idryomov@gmail.com>2017-09-06 13:56:44 -0400
commit95569713afc0b53ded1bba67834e0be24529a8c9 (patch)
tree213f9d7dc7f6420161906cc7c6c8ca18be19e9dc /include/linux/ceph
parent3fb99d483e614bc3834784c7a686572c7970bb92 (diff)
ceph: new cap message flags indicate if there is pending capsnap
These flags tell mds if there is pending capsnap explicitly. Without this explicit notification, mds can only conclude if client has pending capsnap. The method mds use is inefficient and error-prone. Signed-off-by: "Yan, Zheng" <zyan@redhat.com> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'include/linux/ceph')
-rw-r--r--include/linux/ceph/ceph_fs.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/include/linux/ceph/ceph_fs.h b/include/linux/ceph/ceph_fs.h
index edf5b04b918a..d1642a4b4c5e 100644
--- a/include/linux/ceph/ceph_fs.h
+++ b/include/linux/ceph/ceph_fs.h
@@ -669,7 +669,9 @@ enum {
669extern const char *ceph_cap_op_name(int op); 669extern const char *ceph_cap_op_name(int op);
670 670
671/* flags field in client cap messages (version >= 10) */ 671/* flags field in client cap messages (version >= 10) */
672#define CEPH_CLIENT_CAPS_SYNC (0x1) 672#define CEPH_CLIENT_CAPS_SYNC (1<<0)
673#define CEPH_CLIENT_CAPS_NO_CAPSNAP (1<<1)
674#define CEPH_CLIENT_CAPS_PENDING_CAPSNAP (1<<2);
673 675
674/* 676/*
675 * caps message, used for capability callbacks, acks, requests, etc. 677 * caps message, used for capability callbacks, acks, requests, etc.