Increasing CMA Utilization with a GFP Flag
Status from this message: Nacked-by: David Hildenbrand <[email protected]>
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | cma: redirect page allocation to CMAinclude/ include/ include/ +1 more | +74 | 1 reply | |
| 2/2 | zram: allow zram to allocate CMA pagesdrivers/ mm/ | +5 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by.
| Patch | David Hildenbrand | Michal Hocko |
|---|---|---|
| Series | Nacked-by | Nacked-by |
| 1/2 | ||
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] Increasing CMA Utilization with a GFP Flag
The current approach to increasing CMA utilization introduced in commit 16867664936e ("mm,page_alloc,cma: conditionally prefer cma pageblocks for movable allocations") increases CMA utilization by redirecting MIGRATE_MOVABLE allocations to a CMA region, when greater than half of the free pages in a given zone are CMA pages. The issue in this approach is that allocations with type MIGRATE_MOVABLE can still succumb to pinning. To get around this, one approach is to re-direct allocations to the CMA areas, that are known not to be victims of pinning.
To this end, this series brings in __GFP_CMA, which we mark with allocations that we know are safe to be redirected to a CMA area.
Heesub Shin (1):
cma: redirect page allocation to CMA
Vinayak Menon (1):
zram: allow zram to allocate CMA pages
drivers/block/zram/zram_drv.c | 5 +-- include/linux/gfp.h | 15 ++++++++ include/linux/highmem.h | 4 ++- include/linux/mmzone.h | 4 +++ mm/page_alloc.c | 83 +++++++++++++++++++++++++++---------------- mm/zsmalloc.c | 4 +-- 6 files changed, 79 insertions(+), 36 deletions(-)
Signature · 2 lines
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project