doc: document ivshmem & hugepages
Document and give some examples of hugepages support with ivshmem device and server. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
parent
f7a199b2b4
commit
7d4f4bdaf7
|
@ -1293,6 +1293,19 @@ copy the shared memory on migration to the destination host. With
|
||||||
With the @option{peer} case, the device should be detached and then reattached
|
With the @option{peer} case, the device should be detached and then reattached
|
||||||
after migration using the PCI hotplug support.
|
after migration using the PCI hotplug support.
|
||||||
|
|
||||||
|
@subsubsection ivshmem and hugepages
|
||||||
|
|
||||||
|
Instead of specifying the <shm size> using POSIX shm, you may specify
|
||||||
|
a memory backend that has hugepage support:
|
||||||
|
|
||||||
|
@example
|
||||||
|
qemu-system-i386 -object memory-backend-file,size=1G,mem-path=/mnt/hugepages,id=mb1
|
||||||
|
-device ivshmem,memdev=mb1
|
||||||
|
@end example
|
||||||
|
|
||||||
|
ivshmem-server also supports hugepages mount points with the
|
||||||
|
@option{-m} memory path argument.
|
||||||
|
|
||||||
@node direct_linux_boot
|
@node direct_linux_boot
|
||||||
@section Direct Linux Boot
|
@section Direct Linux Boot
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue