[pve-devel] qemu-server:add support for hugetlbfs

[Alexandre DERUMIER]

>>1.) Is there some edivence that it is faster (under realistic workload)?

I known that transparent hugepage can be really a problem with a lot of database (oracle,mysql,redis,..)
I never bench it myself, but I hope that Cesar will do it ;).

Disable transparent hugepage is a solution, but it's disable it for all the vms.

I think that static hugepage can do the job, but it need to be tested.


>>2.) Where do we free/dealloc those hugepages? Are the associated with the KVM 
>>process somehow? 

I'm not sure that when hupage are defined, they use memory by default.

But when the kvm process is starting, the memory is allocated/reserverd for the kvm process, 
and the memory is free up on kvm process stop.


----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Samedi 20 Décembre 2014 09:32:42
Objet: Re: [pve-devel] qemu-server:add support for hugetlbfs

> This add support for manually defined hugepages, 
> which can be faster than transparent hugepages for some workload like 
> databases 

1.) Is there some edivence that it is faster (under realistic workload)? 

2.) Where do we free/dealloc those hugepages? Are the associated with the KVM 
process somehow?