[pve-devel] qemul mlock option

[Stefan Priebe]

even more details:
http://patchwork.ozlabs.org/patch/187624/

Stefan

Am 12.06.2014 19:37, schrieb Alexandre DERUMIER:
> http://git.qemu.org/?p=qemu.git;a=commit;h=888a6bc63c94ef34026399117ebf6a1fa0e7a29a
> "
> Add option to mlock qemu and guest memory
>
> In certain scenario, latency induced by paging is significant and
> memory locking is needed. Also, in the scenario with untrusted
> guests, latency improvement due to mlock is desired.
>
> This patch introduces a following new option to mlock guest and
> qemu memory:
>
> -realtime mlock=on|off
> "
>
>
> ----- Mail original -----
>
> De: "Dietmar Maurer" <dietmar at proxmox.com>
> À: pve-devel at pve.proxmox.com
> Envoyé: Jeudi 12 Juin 2014 19:19:24
> Objet: [pve-devel] qemul mlock option
>
>
>
> Can someone explain if/why we should use qemu option “-realtime mlock=off” ?
> I found no good documentation.
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> _______________________________________________
> pve-devel mailing list
> pve-devel at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>