From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-fs@redhat.com, vgoyal@redhat.com
Subject: Re: [Virtio-fs] Adding notifications vq to the virtio-fs device
Date: Fri, 14 Jun 2019 18:24:15 +0100 [thread overview]
Message-ID: <20190614172414.GJ2785@work-vm> (raw)
In-Reply-To: <20190610160955.GA19995@stefanha-x1.localdomain>
* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> Hi Vivek,
> There is discussion of adding the notifications vq to the virtio-fs
> device so that FUSE Notification messages are possible. This was
> previously discussed on the VIRTIO mailing lists here:
> https://lists.oasis-open.org/archives/virtio-dev/201902/msg00074.html
>
> The main issue is how to handle the case where the device wishes to
> raise notifications but the driver has not supplied enough buffers.
>
> FUSE requires reliable notification delivery. We cannot drop
> notifications.
>
> The mechanism will have to support reliable delivery. For example, the
> device may need to pause further operation until the driver makes
> buffers available again. But this could lead to DoS or deadlocks, so
> care is needed!
>
> I hope this link is useful in restarting the discussion about the
> notifications vq.
In the case we were recently discussing, notification of lock
availability, that's not necessarily a problem; if there's no
space on the notification queue then we stop notifying about
locks until there is some space.
Dave
> Stefan
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2019-06-14 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 16:09 [Virtio-fs] Adding notifications vq to the virtio-fs device Stefan Hajnoczi
2019-06-14 17:24 ` Dr. David Alan Gilbert [this message]
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=20190614172414.GJ2785@work-vm \
--to=dgilbert@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.