From: Vivek Goyal <vgoyal@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com
Cc: mszeredi@redhat.com, dgilbert@redhat.com, vgoyal@redhat.com
Subject: [PATCH v2 0/2] viritofsd: Add support for FUSE_HANDLE_KILLPRIV_V2
Date: Thu, 12 Nov 2020 13:24:16 -0500 [thread overview]
Message-ID: <20201112182418.25395-1-vgoyal@redhat.com> (raw)
Hi,
This is V2 of patches to add support for FUSE_HANDLE_KILLPRIV_V2. This
is basically a feature file server can opt-in. And with xattr enabled,
this improves write performance many fold (jumps from 50MB/s to
300MB/s approx).
kernel patches have now been staged in for-next branch of fuse tree by Miklos.
https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/log/?h=for-next
I tested virtiofsd with these patches and things look good to me.
Posting now for review and inclusion as soon as kernel patches are
merged in 5.11.
Thanks
Vivek
Vivek Goyal (2):
virtiofsd: Save error code early at the failure callsite
viriofsd: Add support for FUSE_HANDLE_KILLPRIV_V2
include/standard-headers/linux/fuse.h | 28 ++++++-
tools/virtiofsd/fuse_common.h | 15 ++++
tools/virtiofsd/fuse_lowlevel.c | 11 ++-
tools/virtiofsd/fuse_lowlevel.h | 1 +
tools/virtiofsd/passthrough_ll.c | 116 +++++++++++++++++++++++---
5 files changed, 153 insertions(+), 18 deletions(-)
--
2.25.4
next reply other threads:[~2020-11-12 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 18:24 Vivek Goyal [this message]
2020-11-12 18:24 ` [PATCH v2 1/2] virtiofsd: Save error code early at the failure callsite Vivek Goyal
2021-02-08 17:05 ` [Virtio-fs] " Dr. David Alan Gilbert
2020-11-12 18:24 ` [PATCH v2 2/2] viriofsd: Add support for FUSE_HANDLE_KILLPRIV_V2 Vivek Goyal
2020-11-19 15:42 ` [Virtio-fs] " Stefan Hajnoczi
2021-02-08 17:35 ` Dr. David Alan Gilbert
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=20201112182418.25395-1-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mszeredi@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).