qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* Creating a vhost-user-vsock backend
@ 2024-08-23 13:19 DUO Labs
  0 siblings, 0 replies; only message in thread
From: DUO Labs @ 2024-08-23 13:19 UTC (permalink / raw)
  To: qemu-devel

I've been studying the example given in `contrib/vhost-user-blk`, and trying to match the code to what is in the standard (https://docs.oasis-open.org/virtio/virtio/v1.3/csd01/virtio-v1.3-csd01.html#x1-3050002), so I can use the code to create my own vhost-user-vsock server.

I think I almost understand it, but I don't get exactly how do you correlate out_sg and in_sg to the header and ancillary data (for virtio-blk, it would either be the data to be written or a buffer to read data into, and vsock would be similar), respectively.

In virtio-blk, I see that there's an inhdr, and outhdr, but vsock doesn't have that, so I'm not sure how to map the same concept. Similarly, does `elem->out_sg[0]` always map to the header, and `elem->out_sg[1]` always map to the ancillary data? What about when you are reading into a buffer --- should it always be read into `elem->in_sg[0]`, or is that only for virtio-blk?


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-08-23 13:20 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-23 13:19 Creating a vhost-user-vsock backend DUO Labs

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).