diff options
author | Mike Rapoport <rppt@linux.ibm.com> | 2021-05-17 21:15:15 +0300 |
---|---|---|
committer | Mike Rapoport <rppt@linux.ibm.com> | 2021-06-30 11:38:33 +0300 |
commit | e2a86800d58639b3acde7eaeb9eb393dca066e08 (patch) | |
tree | 964e0c209239ff75e7aa615af95bade6f1eef368 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | c4681547bcce777daf576925a966ffa824edd09d (diff) | |
download | linux-e2a86800d58639b3acde7eaeb9eb393dca066e08.tar.xz |
memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER
The code that frees unused memory map uses rounds start and end of the
holes that are freed to MAX_ORDER_NR_PAGES to preserve continuity of the
memory map for MAX_ORDER regions.
Lots of core memory management functionality relies on homogeneity of the
memory map within each pageblock which size may differ from MAX_ORDER in
certain configurations.
Although currently, for the architectures that use free_unused_memmap(),
pageblock_order and MAX_ORDER are equivalent, it is cleaner to have common
notation thought mm code.
Replace MAX_ORDER_NR_PAGES with pageblock_nr_pages and update the comments
to make it more clear why the alignment to pageblock boundaries is
required.
Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
Tested-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions