OASIS Open Mailing List Archives  ·  All Lists  ·  virtio  ·  2013-08

virtio — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

*-over-virtio


Sasha Levin <[email protected]> writes: > Hi all, > > 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? Do we have any in the current spec? It's certainly easy to reserve IDs for things which aren't in the spec. Cheers, Rusty.

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]