Re: [PATCH v1 0/4] virtio-msg transport layer

Michael S. Tsirkin
2026-02-20T10:03:29Z

On Fri, Feb 20, 2026 at 06:13:55AM +0000, Parav Pandit wrote:
> > > 4. I dont find the transport messages to read and write to the driver memory supplied in VIRTIO_MSG_SET_VQUEUE addresses to operate
> > the virtqueues.
> > > Dont we need VIRTIO_MEM_READ, VIRTIO_MEM_WRITE request and response?
> >
> > surely this can be an optional transport feature bit.
> >
> How is this optional?
> How can one implement a transport without defining the basic data transfer semantics?
> For example for TCP transporting, driver side OS is implementing header format foo, and device side is using header format bar.
> How does it work?

I'm not sure what do foo/bar refer to, or what TCP transporting means.
The simplest way to do TCP on top of virtio is to layer it above virtio
net. That uses VQs for data transfers.

--
MST