From: Michael Ellerman <michael@ellerman.id.au>
To: Anton Blanchard <anton@samba.org>
Cc: Michael Neuling <mikey@neuling.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: 64bit kernel is huge
Date: Thu, 01 Oct 2009 13:36:16 +1000 [thread overview]
Message-ID: <1254368176.11564.85.camel@concordia> (raw)
In-Reply-To: <20090928074503.GB16073@kryten>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Mon, 2009-09-28 at 17:45 +1000, Anton Blanchard wrote:
> Hi,
>
> I've found at least one machine that wont boot 2.6.31-rc* with a
> pseries_defconfig. If I move real-base from 0xc00000 to 0xd00000 it
> boots fine.
>
> # size vmlinux
> text data bss dec hex filename
> 9812942 1982496 1105228 12900666 c4d93a vmlinux
>
> Looks like we blow right through the 12MB mark. It desperately needs to eat
> less and lose weight.
>
> Here are some of the problem areas:
>
> 131072 lppaca
> 65536 paca
>
> I think we've attacked these before, not sure if there is anything left
> we can trim.
Why can't we dynamically allocate all but one paca? I seem to recall
Mikey tried it but it didn't work?
And on !ISERIES we should be able to allocate the lppacas too I think,
the HV doesn't know about them until register_vpa().
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-10-01 3:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 7:45 64bit kernel is huge Anton Blanchard
2009-09-28 8:07 ` Benjamin Herrenschmidt
2009-09-28 9:13 ` Michael Ellerman
2009-09-30 6:01 ` Michael Neuling
2009-09-30 20:30 ` Benjamin Herrenschmidt
2009-10-01 5:06 ` Michael Neuling
2009-10-01 5:09 ` Michael Neuling
2009-09-30 13:57 ` Arnd Bergmann
2009-10-01 3:36 ` Michael Ellerman [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=1254368176.11564.85.camel@concordia \
--to=michael@ellerman.id.au \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).