Re: [PATCH] mm: memblock: do not enforce current limit for memblock_phys* family

2019-10-14 Thread Mike Rapoport
On October 15, 2019 12:44:23 AM GMT+02:00, Andrew Morton wrote: >On Sun, 13 Oct 2019 00:31:01 +0300 Mike Rapoport >wrote: > >> Until commit 92d12f9544b7 ("memblock: refactor internal allocation >> functions") the maximal address for memblock allocations was forced >to >> memblock.current_limit o

Re: [PATCH] mm: memblock: do not enforce current limit for memblock_phys* family

2019-10-14 Thread Andrew Morton
On Sun, 13 Oct 2019 00:31:01 +0300 Mike Rapoport wrote: > Until commit 92d12f9544b7 ("memblock: refactor internal allocation > functions") the maximal address for memblock allocations was forced to > memblock.current_limit only for the allocation functions returning virtual > address. The changes

[PATCH] mm: memblock: do not enforce current limit for memblock_phys* family

2019-10-12 Thread Mike Rapoport
From: Mike Rapoport Until commit 92d12f9544b7 ("memblock: refactor internal allocation functions") the maximal address for memblock allocations was forced to memblock.current_limit only for the allocation functions returning virtual address. The changes introduced by that commit moved the limit e