[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e9edd1e-6653-a585-0e22-69930a07dce1@de.ibm.com>
Date: Mon, 4 May 2020 16:50:06 +0200
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Marc Hartmayer <mhartmay@...ux.ibm.com>,
linux-s390 <linux-s390@...r.kernel.org>,
Vasily Gorbik <gor@...ux.ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: linux-next: Tree for May 4 --> mm: free_area_init: allow defining
max_zone_pfn in descending order does increase memory use
Mike,
commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow defining max_zone_pfn in descending order")
does increase the memory use on s390 (e.g. 700 MB vs.1.8 GB).
Something is odd in this patch. Any idea?
Powered by blists - more mailing lists