From: Christian Borntraeger <borntraeger@de•ibm.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Mike Rapoport <rppt@linux•ibm.com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Andrew Morton <akpm@linux-foundation•org>,
Marc Hartmayer <mhartmay@linux•ibm.com>,
linux-s390 <linux-s390@vger•kernel.org>,
Vasily Gorbik <gor@linux•ibm.com>,
Heiko Carstens <heiko.carstens@de•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
Date: Tue, 5 May 2020 11:36:14 +0200 [thread overview]
Message-ID: <1631771e-371b-c233-ec0f-056646694c85@de.ibm.com> (raw)
In-Reply-To: <20200505070828.20fd21af@canb.auug.org.au>
On 04.05.20 23:08, Stephen Rothwell wrote:
> Hi Mike,
>
> On Mon, 4 May 2020 18:44:10 +0300 Mike Rapoport <rppt@linux•ibm.com> wrote:
>>
>> Ho Christian,
>>
>> On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote:
>>> 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?
>>
>> Yeah, this patch is buggy. In short, it breaks zone size calculation on
>> s390 and some other architectures.
>>
>> I've just replied at [1] with more details and a fix.
>>
>> [1] https://lore.kernel.org/linux-mm/20200504153901.GM14260@kernel.org/
>
> I have added that to linux-next for today.
>
Ack, 5.7.0-rc4-next-20200505 seems to work fine.
prev parent reply other threads:[~2020-05-05 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 7:35 linux-next: Tree for May 4 Stephen Rothwell
2020-05-04 14:50 ` linux-next: Tree for May 4 --> mm: free_area_init: allow defining max_zone_pfn in descending order does increase memory use Christian Borntraeger
2020-05-04 15:44 ` Mike Rapoport
2020-05-04 21:08 ` Stephen Rothwell
2020-05-05 9:36 ` Christian Borntraeger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1631771e-371b-c233-ec0f-056646694c85@de.ibm.com \
--to=borntraeger@de$(echo .)ibm.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=gor@linux$(echo .)ibm.com \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=mhartmay@linux$(echo .)ibm.com \
--cc=rppt@linux$(echo .)ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox