OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [PATCH v3 0/2] virtio-fs: add notification queue

On Wed, Jun 09, 2021 at 04:37:38PM +0100, Stefan Hajnoczi wrote:
> v3:
>  * Clarify that empty notification vq semantics are documented for all
>    supported notification message types. [Vivek]
>  * Clarify that the device has internal resources for lock requests and when
>    they are exhausted ENOLCK is returned. [Vivek]
> v2:
>  * Document empty virtqueue behavior for FUSE_NOTIFY_LOCK messages
> This patch series adds the notification queue to the VIRTIO specification.
> This new virtqueue carries device->driver FUSE notify messages.  They are
> currently unused but will be necessary for file locking, which can block for an
> unbounded amount of time and therefore needs a asynchronous completion event
> instead of a request/response buffer that consumes space in the request
> virtqueue until the operation completes.
> Patch 1 corrects an oversight I noticed: the file system device was not added
> to the Conformance chapter.
> Stefan Hajnoczi (2):
>   virtio-fs: add file system device to Conformance chapter
>   virtio-fs: add notification queue
>  conformance.tex | 23 ++++++++++++++++
>  virtio-fs.tex   | 71 ++++++++++++++++++++++++++++++++++++++++++-------
>  2 files changed, 84 insertions(+), 10 deletions(-)

I am requesting a vote. Thank you!

Fixes: https://github.com/oasis-tcs/virtio-spec/issues/111


Attachment: signature.asc
Description: PGP signature

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]