Re: [RFC virtio-next 0/4] Introduce CAIF Virtio and reversed Vrings

2012-11-05 Thread Rusty Russell
Sjur Brændeland writes: > Hi Rusty, > >> So, this adds another host-side virtqueue implementation. >> >> Can we combine them together conveniently? You pulled out more stuff >> into vring.h which is a start, but it's a bit overloaded. >> Perhaps we should separate the common fields into struct vr

Re: [RFC virtio-next 0/4] Introduce CAIF Virtio and reversed Vrings

2012-11-05 Thread Sjur Brændeland
Hi Rusty, > So, this adds another host-side virtqueue implementation. > > Can we combine them together conveniently? You pulled out more stuff > into vring.h which is a start, but it's a bit overloaded. > Perhaps we should separate the common fields into struct vring, and use > it to build: > >

Re: [RFC virtio-next 0/4] Introduce CAIF Virtio and reversed Vrings

2012-11-01 Thread Rusty Russell
Sjur Brændeland writes: > Zero-Copy data transport on the modem is primary goal for CAIF Virtio. > In order to achieve Zero-Copy the direction of the Virtio rings are > flipped in the RX direction. So we have implemented the Virtio > access-function similar to what is found in vhost.c. So, this a

[RFC virtio-next 0/4] Introduce CAIF Virtio and reversed Vrings

2012-10-31 Thread Sjur Brændeland
This patch-set introduces the CAIF Virtio Link layer. The purpose is to communicate with a remote processor (a modem) over shared memory. Virtio is used as the transport mechanism, and the Remoteproc framework provides configuration and management of the Virtio rings and devices. The modem and Linu