archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert (git)" <>
Subject: [PATCH 0/3] Fuse definitions for virtiofs
Date: Fri,  2 Aug 2019 18:15:18 +0100	[thread overview]
Message-ID: <> (raw)

From: "Dr. David Alan Gilbert" <>

  Virtiofs is a fuse-over-virtio filesystem to allow
virtual machines to access a fileystem easily, it's
currently in development, and we'd like to try and
get some of our structures and commands stabilised.
Since it runs over virtio, a spec is currently running through
the virtio standardisation process, and they'd like to
see the additional Fuse commands nailed down.  Also we'd
like to stop chasing bit/command number allocation.

The additions included here provide a performance feature
that lets the daemon map files into the hypervisor and thus
guests address space, allowing a DAX like mapping.

  For you following these patches in virtiofs, I've
made three changes:
     a) Remove the unused 'fh' field from removemapping
     b) Change the 'map_alignment' field to be log2(size) and
        use up the current uint16_t padding rather than eating
        a fresh uint32_t
     c) Moved FUSE_MAP_ALIGNMENT along one bit since
        FUSE_EXPLICIT_INVAL_DATA used up bit 25.

    virtiofs home page:
    virtio-fs specification patches:


Dr. David Alan Gilbert (3):
  fuse: Add 'setupmapping'
  fuse: add 'removemapping'
  fuse: Add map_alignment for setup/remove mapping

 include/uapi/linux/fuse.h | 38 +++++++++++++++++++++++++++++++++++++-
 1 file changed, 37 insertions(+), 1 deletion(-)


             reply	other threads:[~2019-08-02 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 17:15 Dr. David Alan Gilbert (git) [this message]
2019-08-02 17:15 ` [PATCH 1/3] fuse: Add 'setupmapping' Dr. David Alan Gilbert (git)
2019-08-02 17:15 ` [PATCH 2/3] fuse: add 'removemapping' Dr. David Alan Gilbert (git)
2019-08-02 17:15 ` [PATCH 3/3] fuse: Add map_alignment for setup/remove mapping Dr. David Alan Gilbert (git)

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).