linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] powerpc: Make the NR_CPUS max 8192
Date: Mon, 18 May 2009 17:01:11 +1000	[thread overview]
Message-ID: <31374.1242630071@neuling.org> (raw)
In-Reply-To: <alpine.LRH.2.00.0905180857060.16754@vixen.sonytel.be>

In message <alpine.LRH.2.00.0905180857060.16754@vixen.sonytel.be> you wrote:
> On Mon, 18 May 2009, Michael Neuling wrote:
> > > > We can compile and boot with NR_CPUS=3D8192, so make this the max.  102
4
> > > > was an arbitrary decision anyway.
> > > 
> > > Is 8192 still arbitrary? Or does something break above that?
> > 
> > Yeah, the compile breaks after that with 4K pages.
> > 
> > In drivers/base/node.c we have:
> > 	/* 2008/04/07: buf currently PAGE_SIZE, need 9 chars per 32 bits. */
> > 	BUILD_BUG_ON((NR_CPUS/32 * 9) > (PAGE_SIZE-1));
> > which causes:
> > drivers/base/node.c: In function 'node_read_cpumap':
> > drivers/base/node.c:31: error: size of array 'type name' is negative
> > 
> > I can compile with 16384 CPUs with 64K pages, but it doesn't boot.  
> > 
> > sfr asked for size info for different builds, so I may as well repost
> > them here:
> > 
> >    text	   data		bss		dec		hex	filenam
e
> > 9237767	3225768		4409996		16873531	101783b	vmlinux
.1024
> > 9247355	4769472		7373708		21390535	14664c7	vmlinux
.2048
> > 9267239	7857032		13301132	30425403	1d0413b	vmlinux
.4096
> > 9302623	14035832	25155980	48494435	2e3f763	vmlinux
.8192
> > 9373283	26389360	48865676	84628319	50b535f	vmlinux
.16384
> 
> Will distros now start pushing NR_CPUS=8192-kernels on us?

Yeah, that's a concern.

Mikey

      reply	other threads:[~2009-05-18  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18  1:13 [PATCH] powerpc: Make the NR_CPUS max 8192 Michael Neuling
2009-05-18  1:24 ` Michael Ellerman
2009-05-18  4:14   ` Michael Neuling
2009-05-18  6:57     ` Geert Uytterhoeven
2009-05-18  7:01       ` Michael Neuling [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=31374.1242630071@neuling.org \
    --to=mikey@neuling.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linuxppc-dev@ozlabs.org \
    --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).