diff options
author | Heiko Carstens <hca@linux.ibm.com> | 2020-07-14 09:22:21 +0300 |
---|---|---|
committer | Heiko Carstens <hca@linux.ibm.com> | 2020-07-20 11:55:40 +0300 |
commit | 771cf196cc92a6078656548bbc073aa932c053ab (patch) | |
tree | 708cd29473c19c6f8ca4bd0fa38edc660614e45d /arch/s390 | |
parent | 3c5f2eb9695cd241c9898a01388b19a149d0b7d2 (diff) | |
download | linux-771cf196cc92a6078656548bbc073aa932c053ab.tar.xz |
s390/mm: allow order 10 allocations
Get rid of FORCE_MAX_ZONEORDER which limited allocations to order 8 (= 1MB)
and use the default, which allows for order 10 (= 4MB) allocations.
Given that s390 allows less than the default this caused some memory
allocation problems more or less unique to s390 from time to time.
Note: this was originally introduced with commit 684de39bd795 ("[S390]
Fix IPL from NSS.") in order to support Named Saved Segments, which
could start/end at an arbitrary 1 megabyte boundary and also before
support for sparsemem vmemmmap was enabled.
Since NSS support is gone, but sparsemem vmemmap support is available
this limitation can go away.
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'arch/s390')
-rw-r--r-- | arch/s390/Kconfig | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig index 7697a1f8e819..0df33cffec52 100644 --- a/arch/s390/Kconfig +++ b/arch/s390/Kconfig @@ -625,10 +625,6 @@ config ARCH_ENABLE_MEMORY_HOTREMOVE config ARCH_ENABLE_SPLIT_PMD_PTLOCK def_bool y -config FORCE_MAX_ZONEORDER - int - default "9" - config MAX_PHYSMEM_BITS int "Maximum size of supported physical memory in bits (42-53)" range 42 53 |