From: Mike Rapoport <rppt@linux.ibm.com>
To: Matt Turner <mattst88@gmail.com>
Cc: Michael Cree <mcree@orcon.net.nz>,
linux-mm@kvack.org, linux-alpha <linux-alpha@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression bisected to fa3354e4ea39 (mm: free_area_init: use maximal zone PFNs rather than zone sizes)
Date: Sat, 31 Jul 2021 12:19:13 +0300 [thread overview]
Message-ID: <YQUVkbhX0U3te1l6@linux.ibm.com> (raw)
In-Reply-To: <CAEdQ38HZ4g_E3vtG=f6p_sfuWnk7haK_eJ0MZziLsOq0ZmfBoQ@mail.gmail.com>
On Fri, Jul 30, 2021 at 12:53:58PM -0700, Matt Turner wrote:
> On Tue, Jul 27, 2021 at 1:41 PM Mike Rapoport <rppt@linux.ibm.com> wrote:
> > On Tue, Jul 27, 2021 at 12:24:26PM -0700, Matt Turner wrote:
> > >
> > > Thanks, this patch fixes it. With the patch applied, I see
> > >
> > > Zone ranges:
> > > DMA [mem 0x0000000000000000-0x00000fffffffdfff]
> > > Normal empty
> > > Movable zone start for each node
> > > Early memory node ranges
> > > node 0: [mem 0x0000000000000000-0x00000001ffffffff]
> > > node 0: [mem 0x0000000400000000-0x00000005ffffffff]
> > > Initmem setup node 0 [mem 0x0000000000000000-0x00000005ffffffff]
> > >
> > > If you want to send me this patch with your S-o-b I'll take it through
> > > my alpha git tree.
> >
> > The patch is on its way :)
>
> Thanks a bunch, Mike, for the patch and for all you do!
>
> > Now I'm really curios how commit e7793e53901b ("arc: update comment about
> > HIGHMEM implementation") will work out.
Oh, sure, I've copied the wrong line from the log :)
> You probably mean fdb7d9b7acd0 ("alpha: remove DISCONTIGMEM and
> NUMA"). Works well so far!
>
> Maybe in some alternative universe where I have infinite free time
> (and my own power plant!) I'll get a second AlphaServer ES47 with the
> enormous "hose" [1] to link the two and I'll poke you for guidance on
> restoring NUMA support :)
Heh, I'm not sure that restoring NUMA on alpha is really good use for free
time even if it were infinite :)
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2021-07-31 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 19:27 Regression bisected to fa3354e4ea39 (mm: free_area_init: use maximal zone PFNs rather than zone sizes) Matt Turner
2021-07-26 20:06 ` Mike Rapoport
2021-07-26 21:23 ` Matt Turner
2021-07-27 6:43 ` Mike Rapoport
2021-07-27 19:24 ` Matt Turner
2021-07-27 20:41 ` Mike Rapoport
2021-07-30 19:53 ` Matt Turner
2021-07-31 9:19 ` Mike Rapoport [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=YQUVkbhX0U3te1l6@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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;
as well as URLs for NNTP newsgroup(s).