From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Ben Hutchings <ben@decadent.org.uk>,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: powerpc/mm: Only define MAX_PHYSMEM_BITS in SPARSEMEM configurations
Date: Mon, 25 Mar 2019 21:12:33 +0100 [thread overview]
Message-ID: <877ecm1zny.fsf@igel.home> (raw)
In-Reply-To: <87a7hjp4oi.fsf@concordia.ellerman.id.au> (Michael Ellerman's message of "Mon, 25 Mar 2019 22:35:41 +1100")
On Mär 25 2019, Michael Ellerman <mpe@ellerman.id.au> wrote:
> So I'm inclined to just switch to always using SPARSEMEM on 64-bit
> Book3S, because that's what's well tested and we hardly need more code
> paths to test. Unless anyone has a strong objection, I haven't actually
> benchmarked FLATMEM vs SPARSEMEM on a G5.
Configuring with SPARSEMEM saves about 32Mb of memory.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-03-25 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 1:17 [PATCH] powerpc/mm: Only define MAX_PHYSMEM_BITS in SPARSEMEM configurations Ben Hutchings
2019-03-22 12:21 ` Michael Ellerman
[not found] ` <44QjSh4zGhz9sV2__48832.6491251186$1553257542$gmane$org@ozlabs.org>
2019-03-24 22:18 ` Andreas Schwab
2019-03-24 23:05 ` Ben Hutchings
2019-03-25 0:03 ` Andreas Schwab
2019-03-25 3:54 ` Ben Hutchings
2019-03-25 11:35 ` Michael Ellerman
2019-03-25 12:03 ` Christophe Leroy
2019-03-25 20:12 ` Andreas Schwab [this message]
2019-04-02 12:57 ` Aneesh Kumar K.V
2019-03-25 8:54 Rui Salvaterra
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=877ecm1zny.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ben@decadent.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).