From: Vivek Goyal <vgoyal@redhat.com>
To: virtio-fs@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: vgoyal@redhat.com, stefanha@redhat.com, dgilbert@redhat.com,
miklos@szeredi.hu
Subject: [PATCH 0/4] [RFC] virtiofs: Add a notification queue
Date: Fri, 15 Nov 2019 15:57:01 -0500 [thread overview]
Message-ID: <20191115205705.2046-1-vgoyal@redhat.com> (raw)
Hi,
These are RFC patches for adding a notification queue to allow sending
notifications from host to guest.
It also adds support for blocking remote posix locks using the newly
introduced notification queue.
These patches apply on top of 5.4-rc8 plus following patch series I had
posted a while back.
https://lkml.org/lkml/2019/10/30/493
These changes require virtio spec changes as well. I have yet to do
that.
Thanks
Vivek
Vivek Goyal (4):
virtiofs: Provide a helper function for virtqueue initialization
virtiofs: Add an index to keep track of first request queue
virtiofs: Add a virtqueue for notifications
virtiofs: Support blocking posix locks (fcntl(F_SETLKW))
fs/fuse/virtio_fs.c | 328 ++++++++++++++++++++++++++++++---
include/uapi/linux/fuse.h | 7 +
include/uapi/linux/virtio_fs.h | 5 +
3 files changed, 310 insertions(+), 30 deletions(-)
--
2.20.1
next reply other threads:[~2019-11-15 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 20:57 Vivek Goyal [this message]
2019-11-15 20:57 ` [PATCH 1/4] virtiofs: Provide a helper function for virtqueue initialization Vivek Goyal
2019-11-15 20:57 ` [PATCH 2/4] virtiofs: Add an index to keep track of first request queue Vivek Goyal
2019-11-21 16:00 ` Stefan Hajnoczi
2019-11-21 16:00 ` Stefan Hajnoczi
2019-11-15 20:57 ` [PATCH 3/4] virtiofs: Add a virtqueue for notifications Vivek Goyal
2019-11-15 20:57 ` [PATCH 4/4] virtiofs: Support blocking posix locks (fcntl(F_SETLKW)) Vivek Goyal
2019-11-21 17:00 ` Stefan Hajnoczi
2019-11-22 13:00 ` Vivek Goyal
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=20191115205705.2046-1-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=dgilbert@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=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 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).