Re: Collapse all Print all In new window Guaranteed allocation of huge pages (1G) using movablecore=N doesn't seem to work at all.

Sorry for garbaged title - I copy & pased from older mail which I by mistake sent in HTML (had to use gmail web interface here) Beset regards, Maxim Levitsky On Sat, Nov 4, 2017 at 1:31 AM, Maxim Levitsky wrote: > Hi! > > My system has 64G of ram and I want to

Re: Collapse all Print all In new window Guaranteed allocation of huge pages (1G) using movablecore=N doesn't seem to work at all.

Sorry for garbaged title - I copy & pased from older mail which I by mistake sent in HTML (had to use gmail web interface here) Beset regards, Maxim Levitsky On Sat, Nov 4, 2017 at 1:31 AM, Maxim Levitsky wrote: > Hi! > > My system has 64G of ram and I want to create 32 1G huge pages

Collapse all Print all In new window Guaranteed allocation of huge pages (1G) using movablecore=N doesn't seem to work at all.

Hi! My system has 64G of ram and I want to create 32 1G huge pages to use in KVM virtualization, on demand, only when VM is running. So I booted the kernel with 'hugepagesz=1G hugepages=0 default_hugepagesz=1G movablecore=40G' However I still can't allocate the pages reliably. For instance this

Collapse all Print all In new window Guaranteed allocation of huge pages (1G) using movablecore=N doesn't seem to work at all.

Hi! My system has 64G of ram and I want to create 32 1G huge pages to use in KVM virtualization, on demand, only when VM is running. So I booted the kernel with 'hugepagesz=1G hugepages=0 default_hugepagesz=1G movablecore=40G' However I still can't allocate the pages reliably. For instance this