Re: [Qemu-devel] Why I advise against using ivshmem

[Paolo Bonzini <pbonzini@redhat.com>]

Il 12/06/2014 18:02, Vincent JARDIN ha scritto:
>
>> * Get all the required parts outside QEMU packaged in major distros, or
>>    absorbed into QEMU
>
> Redhat did disable it. why? it is there in QEMU.

We don't ship everything that is part of QEMU, just like we selectively 
disable many drivers in Linux.

Markus especially referred to parts *outside* QEMU: the server, the uio 
driver, etc.  These out-of-tree, non-packaged parts of ivshmem are one 
of the reasons why Red Hat has disabled ivshmem in RHEL7.

He also listed many others.  Basically for parts of QEMU that are not of 
high quality, we either fix them (this is for example what we did for 
qcow2) or disable them.  Not just ivshmem suffered this fate, for 
example many network cards, sound cards, SCSI storage adapters.

Now, vhost-user is in the process of being merged for 2.1.  Compared to 
the DPDK solution:

* it doesn't require hugetlbfs (which only enabled shared memory by 
chance in older QEMU releases, that was never documented)

* it doesn't require ivshmem (it does require shared memory, which will 
also be added to 2.1)

* it doesn't require the kernel driver from the DPDK sample

* it is not just shared memory, but also defines an interface to use it 
(another of Markus's points)

vhost-user is superior, and it is superior because it has been designed 
from the get-go through cooperation of all interested parties (namely 
QEMU and snabbswitch).

Paolo