| commit | 3c5f2eb9695cd241c9898a01388b19a149d0b7d2 | [log] [tgz] |
|---|---|---|
| author | Heiko Carstens <hca@linux.ibm.com> | Tue Jul 14 07:46:40 2020 +0200 |
| committer | Heiko Carstens <hca@linux.ibm.com> | Mon Jul 20 10:55:32 2020 +0200 |
| tree | a71a73963bfe622b0def696bc762911af28405ee | |
| parent | a709423f7a3a452e5fa7442425817c1bdccd7926 [diff] |
s390/mm: avoid trimming to MAX_ORDER Trimming to MAX_ORDER was originally done in order to avoid to set HOLES_IN_ZONE, which in turn would enable a quite expensive pfn_valid() check. pfn_valid() however only checks if a struct page exists for a given pfn. With sparsemen vmemmap there are always struct pages, since memmaps are allocated for whole sections. Therefore remove the HOLES_IN_ZONE comment and the trimming. Signed-off-by: Heiko Carstens <hca@linux.ibm.com>