Displaying 3 results from an estimated 3 matches for "36a0f558".
2014 Jun 18
0
[Qemu-devel] Why I advise against using ivshmem
...ations using regular networking APIs.
Stefan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20140618/36a0f558/attachment-0001.sig>
2014 Jun 17
4
[Qemu-devel] Why I advise against using ivshmem
Hello all,
On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote:
> ivshmem has a performance disadvantage for guest-to-host
> communication. Since the shared memory is exposed as PCI BARs, the
> guest has to memcpy into the shared memory.
>
> vhost-user can access guest memory directly and avoid the copy inside the guest.
Actually, you can avoid this memory copy using frameworks like
2014 Jun 17
4
[Qemu-devel] Why I advise against using ivshmem
Hello all,
On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote:
> ivshmem has a performance disadvantage for guest-to-host
> communication. Since the shared memory is exposed as PCI BARs, the
> guest has to memcpy into the shared memory.
>
> vhost-user can access guest memory directly and avoid the copy inside the guest.
Actually, you can avoid this memory copy using frameworks like