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: [virtio-dev] [PATCH v5 01/10] vhost-user: add vhost-user device type


On 27/7/20 3:25 Î.Î., Stefan Hajnoczi wrote:

On Fri, Jul 24, 2020 at 08:31:48PM +0300, Nikos Dragazis wrote:
On 24/7/20 5:41 Î.Î., Michael S. Tsirkin wrote:
On Fri, Jul 17, 2020 at 10:26:35AM +0100, Stefan Hajnoczi wrote:
So how about XXX notifications for both of these things?
Where XXX explains what is the reason for triggering each
type of notification.
I guess Stefan introduced the term "doorbell" because it is a widely
used term (e.g., in NVMe devices) and I think it is a pretty good
term. However, I agree that the vague term "notification" may cause
confusion.

Replacing "doorbells" and "notifications" with "XXX notifications"
sounds good. I can't think of some good terms for XXX right now.
Feel free to propose.
Device-specific notifications and device-specific doorbells?

I think these concepts should be part of the core VIRTIO device model so
that other devices can also define device-specific
notifications/doorbells in the future.

Stefan

I think that Michael is OK with standardizing these resources, but he is
not really happy with the term "doorbell".

From the one hand, using the term "XXX notification" would be more
consistent with the virtio spec, since virtio already uses the term
"notification" for driver-to-device signaling regarding the virtqueues.

On the other hand, I can't find something for XXX that would sound
better than "doorbell".

But let's see what Michael has to say.

Nikos


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