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


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

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

Subject: Re: [virtio-comment] *-over-virtio

On Mon, Aug 05, 2013 at 12:22:06PM -0400, Sasha Levin wrote:
> We seem to have a family of several devices that are rather simple on the virtio level. Some
> identifying features include:
>  * No real usage of the configuration space
>  * No device features
>  * No control vqs
>  * Usually one, but possibly 2 vqs used for straightforward message passing outside the virtio
> scope.
> The use case is simple: use virtio as a simple transport for protocol specific messages, this
> can pretty much go over any other transport exactly the same way.
> Would it make sense to move their actual definition out of the spec and just reserve device
> IDs for them there?

Why don't they use virtio-serial or the new vsock from the start?  Both
transports are built to support arbitrary protocols for tasks that don't
need virtio device-level features.  Seems like the right fit instead of
reserving unique virtio device IDs.


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