LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Mike Travis <travis@sgi.com>
Cc: ioe-lkml@rameria.de, akpm@linux-foundation.org, ak@suse.de,
mingo@elte.hu, clameter@sgi.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] x86: Add config variables for SMP_MAX
Date: Mon, 28 Jan 2008 10:45:20 -0600 [thread overview]
Message-ID: <20080128104520.e1e6c878.pj@sgi.com> (raw)
In-Reply-To: <479108C3.1010800@sgi.com>
Ten days ago, Mike wrote:
> The primary problem arises because of cpumask_t local variables. Until I
> can deal with these, increasing NR_CPUS to a really large value increases
> stack size dramatically.
>
> Here are the top stack consumers with NR_CPUS = 4k.
>
> 16392 isolated_cpu_setup
> 10328 build_sched_domains
The problem in kernel/sched.c:isolated_cpu_setup() is an array of
NR_CPUS integers:
static int __init isolated_cpu_setup(char *str)
{
int ints[NR_CPUS], i;
str = get_options(str, ARRAY_SIZE(ints), ints);
Since isolated_cpu_setup() is an __init routine, perhaps we could
make that ints[] array static __initdata?
The build_sched_domains() may require more thought and code rework.
See also the lkml discussion of my patches that reworked the cpuset
code implementing 'sched_load_balance' calling into build_sched_domains
() via kernel/sched.c:partition_sched_domains(). This is not performance
critical code, fortunately.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-01-28 16:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 18:30 [PATCH 0/5] x86: Reduce memory usage for large count NR_CPUs fixup travis
2008-01-18 18:30 ` [PATCH 1/5] x86: Change size of node ids from u8 to u16 fixup travis
2008-01-18 19:56 ` Jan Engelhardt
2008-01-18 19:59 ` Mike Travis
2008-01-19 4:03 ` Yinghai Lu
2008-01-19 4:36 ` David Rientjes
2008-01-19 4:43 ` Yinghai Lu
2008-01-19 5:17 ` David Rientjes
2008-01-19 6:20 ` Yinghai Lu
2008-01-19 21:25 ` Mike Travis
2008-01-19 22:33 ` David Rientjes
2008-01-20 0:41 ` Mike Travis
2008-01-20 1:31 ` Yinghai Lu
2008-01-20 6:22 ` David Rientjes
2008-01-18 18:30 ` [PATCH 2/5] x86: Change NR_CPUS arrays in numa_64 fixup travis
2008-01-18 18:30 ` [PATCH 3/5] x86: Change bios_cpu_apicid to percpu data variable fixup travis
2008-01-18 18:30 ` [PATCH 4/5] x86: Add config variables for SMP_MAX travis
2008-01-18 20:04 ` Ingo Oeser
2008-01-18 20:10 ` Christoph Lameter
2008-01-18 20:14 ` Mike Travis
2008-01-18 20:36 ` Andi Kleen
2008-01-18 20:48 ` Mike Travis
2008-01-18 21:02 ` [PATCH 4/5] x86: Add config variables for SMP_MAX II Andi Kleen
2008-01-18 20:48 ` [PATCH 4/5] x86: Add config variables for SMP_MAX Ingo Molnar
2008-01-18 20:55 ` Mike Travis
2008-01-18 20:58 ` Andi Kleen
2008-01-28 16:45 ` Paul Jackson [this message]
2008-01-28 17:00 ` Andi Kleen
2008-01-18 20:46 ` Ingo Molnar
2008-01-19 14:52 ` Ingo Molnar
2008-01-19 15:15 ` Ingo Molnar
2008-01-19 15:24 ` Ingo Molnar
2008-01-19 21:52 ` Mike Travis
2008-01-19 23:24 ` Mike Travis
2008-01-20 1:14 ` Mike Travis
2008-01-19 21:39 ` Mike Travis
2008-01-18 18:30 ` [PATCH 5/5] x86: Add debug of invalid per_cpu map accesses travis
2008-01-18 18:33 ` Andi Kleen
2008-01-18 18:49 ` Mike Travis
2008-01-18 18:56 ` Christoph Lameter
2008-01-18 20:49 ` Ingo Molnar
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=20080128104520.e1e6c878.pj@sgi.com \
--to=pj@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=travis@sgi.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 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).