linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: tony@bakeyournoodle.com (Tony Breeds)
To: Michael Ellerman <michael@ellerman.id.au>
Cc: LinuxPPC-dev <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Increase the upper bound on NR_CPUS.
Date: Thu, 29 Nov 2007 15:23:14 +1100	[thread overview]
Message-ID: <20071129042314.GN24243@bakeyournoodle.com> (raw)
In-Reply-To: <1196309836.7875.3.camel@concordia>

On Thu, Nov 29, 2007 at 03:17:16PM +1100, Michael Ellerman wrote:
> On Thu, 2007-11-29 at 15:16 +1100, Tony Breeds wrote:
> > Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
> > 
> > ---
> > why not?
> 
> How big is say a pseries_defconfig with NR_CPUS = 1024 ?

This is a ppc64_defconfig, with a couple of extra patches, and
NR_CPUS=1024

tony@Sprygo:~/scratch/working$ size ../working_out/arch/powerpc/boot/zImage.{pmac,pseries,iseries} ../working_out/vmlinux
   text    data     bss      dec     hex filename
3697092    5356   48232  3750680  393b18 ../working_out/arch/powerpc/boot/zImage.pmac
3697092    5356   48232  3750680  393b18 ../working_out/arch/powerpc/boot/zImage.pseries
8101340 4994176  815544 13911060  d44414 ../working_out/arch/powerpc/boot/zImage.iseries
8101340 4994176  815544 13911060  d44414 ../working_out/vmlinux

Yours Tony

  linux.conf.au        http://linux.conf.au/ || http://lca2008.linux.org.au/
  Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!

  reply	other threads:[~2007-11-29  4:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  4:16 [PATCH] Increase the upper bound on NR_CPUS Tony Breeds
2007-11-29  4:17 ` Michael Ellerman
2007-11-29  4:23   ` Tony Breeds [this message]
2007-11-29  4:44     ` Michael Ellerman
2007-11-29  6:23 ` Stephen Rothwell
2007-11-29 10:33 ` Arnd Bergmann

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=20071129042314.GN24243@bakeyournoodle.com \
    --to=tony@bakeyournoodle.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@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).