> On Fri, 2010-01-22 at 16:19 +1300, Michael Neuling wrote:
> >=20
> > In message <39fb8f1aeab9940b86c940b9a5f8e6bd41ec316c.1263368253.git.micha=
> e...@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 "t
On Fri, 2010-01-22 at 16:19 +1300, Michael Neuling wrote:
>
> In message
> <39fb8f1aeab9940b86c940b9a5f8e6bd41ec316c.1263368253.git.mich...@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"). Curren
In message <39fb8f1aeab9940b86c940b9a5f8e6bd41ec316c.1263368253.git.mich...@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
On Thu, 2010-01-14 at 11:26 +1100, Michael Neuling 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
> 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 av
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
