From: Ioannis Angelakopoulos <iangelak@redhat.com>
To: linux-fsdevel@vger.kernel.org, virtio-fs@redhat.com
Cc: miklos@szeredi.hu, stefanha@redhat.com, vgoyal@redhat.com
Subject: [PATCH 0/3] Virtiofs: Support for remote blocking posix locks
Date: Wed, 16 Jun 2021 12:08:33 -0400 [thread overview]
Message-ID: <20210616160836.590206-1-iangelak@redhat.com> (raw)
Adding support for remote blocking locks in virtiofs. Initially linux
only supported the fcntl(SETLK) option. Now the fcntl(SETLKW) option
is also supported.
A guest issuing a fcntl(SETLKW) system call will block if another guest
has already acquired the lock. Once the lock is available then the
blocking guest will receive a notification, through the notification
queue. Then the guest will unblock and acquire the lock.
Vivek Goyal (3):
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 | 290 +++++++++++++++++++++++++++++++--
include/uapi/linux/fuse.h | 7 +
include/uapi/linux/virtio_fs.h | 5 +
3 files changed, 288 insertions(+), 14 deletions(-)
--
2.27.0
next reply other threads:[~2021-06-16 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 16:08 Ioannis Angelakopoulos [this message]
2021-06-16 16:08 ` [PATCH 1/3] virtiofs: Add an index to keep track of first request queue Ioannis Angelakopoulos
2021-06-18 7:43 ` Miklos Szeredi
2021-06-18 15:52 ` Vivek Goyal
2021-06-16 16:08 ` [PATCH 2/3] virtiofs: Add a virtqueue for notifications Ioannis Angelakopoulos
2021-06-16 16:08 ` [PATCH 3/3] virtiofs: Support blocking posix locks (fcntl(F_SETLKW)) Ioannis Angelakopoulos
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=20210616160836.590206-1-iangelak@redhat.com \
--to=iangelak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stefanha@redhat.com \
--cc=vgoyal@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).