From: Miklos Szeredi <miklos@szeredi.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Stefan Hajnoczi <stefanha@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: [GIT PULL] add virtio-fs
Date: Thu, 26 Sep 2019 10:43:40 +0200 [thread overview]
Message-ID: <20190926084340.GB1904@miu.piliscsaba.redhat.com> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git tags/virtio-fs-5.4
[There's a trivial merge conflict under Documentation/]
Virtio-fs allows exporting directory trees on the host and mounting them in
guest(s).
This isn't actually a new filesystem, but a glue layer between the fuse
filesystem and a virtio based back-end.
It's similar in functionality to the existing virtio-9p solution, but
significantly faster in benchmarks and has better POSIX compliance.
Further permformance improvements can be achieved by sharing the page cache
between host and guest, allowing for faster I/O and reduced memory use.
Kata Containers have been including the out-of-tree virtio-fs (with the
shared page cache patches as well) since version 1.7 as an experimental
feature. They have been active in development and plan to switch from
virtio-9p to virtio-fs as their default solution. There has been interest
from other sources as well.
The userspace infrastructure is slated to be merged into qemu once the
kernel part hits mainline.
This was developed by Vivek Goyal, Dave Gilbert and Stefan Hajnoczi.
Thanks,
Miklos
---
Dr. David Alan Gilbert (1):
fuse: reserve values for mapping protocol
Stefan Hajnoczi (2):
virtio-fs: add Documentation/filesystems/virtiofs.rst
virtio-fs: add virtiofs filesystem
---
Documentation/filesystems/index.rst | 10 +
Documentation/filesystems/virtiofs.rst | 60 ++
MAINTAINERS | 12 +
fs/fuse/Kconfig | 11 +
fs/fuse/Makefile | 1 +
fs/fuse/fuse_i.h | 9 +
fs/fuse/inode.c | 4 +
fs/fuse/virtio_fs.c | 1195 ++++++++++++++++++++++++++++++++
include/uapi/linux/fuse.h | 8 +-
include/uapi/linux/virtio_fs.h | 19 +
include/uapi/linux/virtio_ids.h | 1 +
11 files changed, 1329 insertions(+), 1 deletion(-)
create mode 100644 Documentation/filesystems/virtiofs.rst
create mode 100644 fs/fuse/virtio_fs.c
create mode 100644 include/uapi/linux/virtio_fs.h
next reply other threads:[~2019-09-26 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 8:43 Miklos Szeredi [this message]
2019-09-27 23:00 ` [GIT PULL] add virtio-fs pr-tracker-bot
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=20190926084340.GB1904@miu.piliscsaba.redhat.com \
--to=miklos@szeredi.hu \
--cc=dgilbert@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@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).