diff options
author | 2024-06-11 00:15:28 +0900 | |
---|---|---|
committer | 2024-07-03 19:30:08 -0700 | |
commit | afb90a36c643112bc8cabefb71c110ee2b757ca3 (patch) | |
tree | 18aa1a1a53eab0ffac62db798564b47c066ae9af /mm/memcontrol.c | |
parent | mm/vmscan: avoid split lazyfree THP during shrink_folio_list() (diff) | |
download | wireguard-linux-afb90a36c643112bc8cabefb71c110ee2b757ca3.tar.xz wireguard-linux-afb90a36c643112bc8cabefb71c110ee2b757ca3.zip |
mm/sparse: use MEMBLOCK_ALLOC_ACCESSIBLE enum instead of 0
Setting 'limit' variable to 0 might seem like it means "no limit". But in
the memblock API, 0 actually means the 'MEMBLOCK_ALLOC_ACCESSIBLE' enum,
which limits the physical address range end based on
'memblock.current_limit'. This could be confusing.
Use the enum instead of 0 to make it clear.
Link: https://lkml.kernel.org/r/20240610151528.943680-1-lsahn@wewakecorp.com
Signed-off-by: Leesoo Ahn <lsahn@ooseel.net>
Acked-by: Mike Rapoport (IBM) <rppt@kernel.org>
Reviewed-by: Wei Yang <richard.weiyang@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'mm/memcontrol.c')
0 files changed, 0 insertions, 0 deletions