| commit | 792fc49787cb7df13f1c38d3e25c863e1c3a6bb2 | |
| author | Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> | |
| Tue, 6 May 2014 15:54:18 +0000 (6 21:24 +0530) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Fri, 30 May 2014 12:26:24 +0000 (30 14:26 +0200) | ||
| tree | 5f1708c709983a84b7c76d26a8a8b96f522c45d1 | treesnapshot (tar.gz zip) |
| parent | 9916d57e64a49d85bcffe272478f869b8fe1583a | commitdiff |
KVM: PPC: BOOK3S: HV: Prefer CMA region for hash page table allocation
Today when KVM tries to reserve memory for the hash page table it
allocates from the normal page allocator first. If that fails it
falls back to CMA's reserved region. One of the side effects of
this is that we could end up exhausting the page allocator and
get linux into OOM conditions while we still have plenty of space
available in CMA.
This patch addresses this issue by first trying hash page table
allocation from CMA's reserved region before falling back to the normal
page allocator. So if we run out of memory, we really are out of memory.
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
Today when KVM tries to reserve memory for the hash page table it
allocates from the normal page allocator first. If that fails it
falls back to CMA's reserved region. One of the side effects of
this is that we could end up exhausting the page allocator and
get linux into OOM conditions while we still have plenty of space
available in CMA.
This patch addresses this issue by first trying hash page table
allocation from CMA's reserved region before falling back to the normal
page allocator. So if we run out of memory, we really are out of memory.
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Alexander Graf <agraf@suse.de>
| arch/powerpc/kvm/book3s_64_mmu_hv.c | diffblobblamehistory |