From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
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 07:08:28 +1000 [thread overview]
Message-ID: <20200505070828.20fd21af@canb.auug.org.au> (raw)
In-Reply-To: <20200504154410.GF342687@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-04 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200504173547.2cdd83bf@canb.auug.org.au>
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 [this message]
2020-05-05 9:36 ` Christian Borntraeger
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=20200505070828.20fd21af@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
--cc=rppt@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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