On Tue, Oct 5, 2010 at 15:40, Guido Trotter <[email protected]> wrote: > On Tue, Oct 5, 2010 at 2:35 PM, <[email protected]> wrote: > >> From: Miguel Di Ciurcio Filho <[email protected]> >> >> Using transparent hugepages, KVM instances can get a good performance boost. >> To activate that, we need to pass the -mem-path argument to KVM along with >> the mount point of the hugetlbfs file system on the node. >> >> For the sake of memory availability computation, we use the -mem-prealloc >> argument when enabling hugepages, so KVM will reserve all hugepages it >> needs when it starts. This avoids allocating an instance on a node that >> will not have enough pages in case other instance needs more than what >> is available after it boots. >> >> Signed-off-by: Miguel Di Ciurcio Filho <[email protected]> > > LGTM (and applied) > > Note that I changed the commit message from "transparent hugepages" to > "hugepages" because transparent hugepages is a separate kernel patch > to avoid the need to use hugetlbfs altogether.
Hmm, did you apply with the two extend calls? Those could have been collapsed into one… iustin
