On 2019/2/19 下午4:28, Vincenzo Maffione wrote:
Il giorno mar 19 feb 2019 alle ore 07:48 Jason Wang
ha scritto:
On 2019/2/18 下午7:53, Vincenzo Maffione wrote:
Hi Jason,
Thanks for the quick reply.
My PV device (to be open sourced soon) uses the QEMU net backend
interface,
in a way simil
Il giorno mar 19 feb 2019 alle ore 07:48 Jason Wang
ha scritto:
>
> On 2019/2/18 下午7:53, Vincenzo Maffione wrote:
> > Hi Jason,
> >Thanks for the quick reply.
> >
> > My PV device (to be open sourced soon) uses the QEMU net backend
> interface,
> > in a way similar to virtio-net.
> > For exam
On 2019/2/18 下午7:53, Vincenzo Maffione wrote:
Hi Jason,
Thanks for the quick reply.
My PV device (to be open sourced soon) uses the QEMU net backend interface,
in a way similar to virtio-net.
For example it uses qemu_set_offload(), qemu_has_vnet_hdr_len(),
qemu_using_vnet_hdr(), qemu_send_p
Hi Jason,
Thanks for the quick reply.
My PV device (to be open sourced soon) uses the QEMU net backend interface,
in a way similar to virtio-net.
For example it uses qemu_set_offload(), qemu_has_vnet_hdr_len(),
qemu_using_vnet_hdr(), qemu_send_packet(), etc.
This means that the device itself doe
On 2019/2/16 上午1:46, Vincenzo Maffione wrote:
Hi,
I was doing experiments with a custom paravirtualized net device,
and I ran into a limitation of the TAP backend. I see from the kernel
code that it is not possible to set the TAP virtio-net header
length to something different from 10 or 12,
Hi,
I was doing experiments with a custom paravirtualized net device,
and I ran into a limitation of the TAP backend. I see from the kernel
code that it is not possible to set the TAP virtio-net header
length to something different from 10 or 12, which means that it
is not possible to set it to 0