From: Michael Ellerman <michael@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH] powerpc: Dynamically allocate pacas
Date: Wed, 27 Jan 2010 14:06:52 +1100 [thread overview]
Message-ID: <1264561612.14310.15.camel@concordia> (raw)
In-Reply-To: <31712.1264130388@neuling.org>
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
On Fri, 2010-01-22 at 16:19 +1300, Michael Neuling wrote:
>
> In message <39fb8f1aeab9940b86c940b9a5f8e6bd41ec316c.1263368253.git.michael@ell
> erman.id.au> you wrote:
> > On 64-bit kernels we currently have a 512 byte struct paca_struct for
> > each cpu (usually just called "the paca"). Currently they are statically
> > allocated, which means a kernel built for a large number of cpus will
> > waste a lot of space if it's booted on a machine with few cpus.
> >
> > We can avoid that by only allocating the number of pacas we need at
> > boot. However this is complicated by the fact that we need to access
> > the paca before we know how many cpus there are in the system.
> >
> > The solution is to dynamically allocate enough space for NR_CPUS pacas,
> > but then later in boot when we know how many cpus we have, we free any
> > unused pacas.
> >
> > Lightly booted on Legacy iSeries & pSeries LPAR.
>
> This is broken on 32bit CPUs. Dies at compile time with
> mpc86xx_defconfig. No paca on 32bit :-(
Bah, who really uses 32-bit anyway ..
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-01-27 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 7:37 [RFC/PATCH] powerpc: Dynamically allocate pacas Michael Ellerman
2010-01-14 0:26 ` Michael Neuling
2010-01-14 0:30 ` Michael Ellerman
2010-01-22 3:19 ` Michael Neuling
2010-01-27 3:06 ` Michael Ellerman [this message]
2010-01-27 3:10 ` Michael Neuling
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=1264561612.14310.15.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@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).