From: Andrew Morton <akpm@digeo.com>
To: Anton Blanchard <anton@samba.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Dave Hansen <haveblue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [lart] /bin/ps output
Date: Sun, 13 Oct 2002 12:25:10 -0700 [thread overview]
Message-ID: <3DA9C896.621CC3D3@digeo.com> (raw)
In-Reply-To: 20021012040959.GE7050@krispykreme
Anton Blanchard wrote:
>
> > Bah! I'm at a competitive disadvantage because I've got a lesser
> > BITS_PER_LONG. No matter, NR_CPUS > BITS_PER_LONG shall be conquered
> > and the explosion of kernel threads will be quite visible (though
> > unfortunately probably post-freeze).
>
> Speaking of which, the recent CONFIG_NR_CPUS addition shows just how
> bloated all our [NR_CPU] structures are. We need to get serious about
> using the per cpu data stuff. Going from 32 to 64 was over 500kB on my
> ppc64 build.
>
Half of which is in timer.c.
mnm:/usr/src/25> size kernel/timer.o
text data bss dec hex filename
4960 100 167648 172708 2a2a4 kernel/timer.o
That's with NR_CPUS=32. Show me yours.
Using the percpu stuff will not significantly reduce this. Some
new data structure might be needed.
next prev parent reply other threads:[~2002-10-13 19:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-12 3:36 [lart] /bin/ps output Dave Hansen
2002-10-12 3:38 ` David S. Miller
2002-10-12 3:55 ` Rik van Riel
2002-10-12 11:49 ` Alan Cox
2002-10-12 3:43 ` William Lee Irwin III
2002-10-12 3:51 ` Anton Blanchard
2002-10-12 3:59 ` William Lee Irwin III
2002-10-12 4:09 ` Anton Blanchard
2002-10-12 6:53 ` David S. Miller
2002-10-12 20:15 ` Richard Henderson
2002-10-13 6:27 ` David S. Miller
2002-10-13 6:42 ` Anton Blanchard
2002-10-13 18:25 ` Richard Henderson
2002-10-13 19:25 ` Andrew Morton [this message]
2002-10-19 12:22 ` Anton Blanchard
2002-11-16 9:24 ` William Lee Irwin III
2002-11-17 0:11 ` Alan Cox
2002-11-16 23:52 ` Chris Wedgwood
2002-11-17 0:11 ` William Lee Irwin III
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=3DA9C896.621CC3D3@digeo.com \
--to=akpm@digeo.com \
--cc=anton@samba.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.