From: Stefan Hajnoczi <stefanha@redhat.com>
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [PATCH 1/2] fuse: drop unused struct fuse_setupmapping_out
Date: Thu, 25 Jul 2019 15:20:13 +0100 [thread overview]
Message-ID: <20190725142014.1726-2-stefanha@redhat.com> (raw)
In-Reply-To: <20190725142014.1726-1-stefanha@redhat.com>
Originally the idea was that FUSE_SETUPMAPPING returns a list of
addresses where the mmaps were made. But then we decided to let the
FUSE client decide where to map so it already knows the address.
Consequently this struct is unused.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
include/uapi/linux/fuse.h | 8 --------
1 file changed, 8 deletions(-)
diff --git a/include/uapi/linux/fuse.h b/include/uapi/linux/fuse.h
index 562a36add1e2..8c36aadb6294 100644
--- a/include/uapi/linux/fuse.h
+++ b/include/uapi/linux/fuse.h
@@ -824,7 +824,6 @@ struct fuse_copy_file_range_in {
uint64_t flags;
};
-#define FUSE_SETUPMAPPING_ENTRIES 8
#define FUSE_SETUPMAPPING_FLAG_WRITE (1ull << 0)
#define FUSE_SETUPMAPPING_FLAG_READ (1ull << 1)
struct fuse_setupmapping_in {
@@ -840,13 +839,6 @@ struct fuse_setupmapping_in {
uint64_t moffset;
};
-struct fuse_setupmapping_out {
- /* Offsets into the cache of mappings */
- uint64_t coffset[FUSE_SETUPMAPPING_ENTRIES];
- /* Lengths of each mapping */
- uint64_t len[FUSE_SETUPMAPPING_ENTRIES];
-};
-
struct fuse_removemapping_in {
/* An already open handle */
uint64_t fh;
--
2.21.0
next prev parent reply other threads:[~2019-07-25 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 14:20 [Virtio-fs] [PATCH 0/2] virtio-fs: fuse.h cleanups Stefan Hajnoczi
2019-07-25 14:20 ` Stefan Hajnoczi [this message]
2019-07-25 14:20 ` [Virtio-fs] [PATCH 2/2] fuse: make FUSE_REMOVEMAPPING_MAX_ENTRY private Stefan Hajnoczi
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=20190725142014.1726-2-stefanha@redhat.com \
--to=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.