LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu> To: Mike Travis <travis@sgi.com> Cc: Ingo Oeser <ioe-lkml@rameria.de>, Andrew Morton <akpm@linux-foundation.org>, Andi Kleen <ak@suse.de>, Christoph Lameter <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: Fri, 18 Jan 2008 21:48:45 +0100 [thread overview] Message-ID: <20080118204845.GD3079@elte.hu> (raw) In-Reply-To: <479108C3.1010800@sgi.com> * Mike Travis <travis@sgi.com> wrote: > >> +config THREAD_ORDER > >> + int "Kernel stack size (in page order)" > >> + range 1 3 > >> + depends on X86_64_SMP > >> + default "3" if X86_SMP_MAX > >> + default "1" > >> + help > >> + Increases kernel stack size. > >> + > > > > Could you please elaborate, why this is needed and put more info > > about this requirement into this patch description? > > > > People worked hard to push data allocation from stack to heap to > > make THREAD_ORDER of 0 and 1 possible. So why increase it again and > > why does this help scalability? > > > > Many thanks and Best Regards > > > > Ingo Oeser, puzzled a bit :-) > > > 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. those should be fixed: > Here are the top stack consumers with NR_CPUS = 4k. > > 16392 isolated_cpu_setup > 10328 build_sched_domains > 8248 numa_initmem_init > 4664 cpu_attach_domain > 4104 show_shared_cpu_map > 3656 centrino_target > 3608 powernowk8_cpu_init > 3192 sched_domain_node_span > 3144 acpi_cpufreq_target > 2584 __svc_create_thread > 2568 cpu_idle_wait > 2136 netxen_nic_flash_print > 2104 powernowk8_target > 2088 _cpu_down > 2072 cache_add_dev > 2056 get_cur_freq > 0 acpi_processor_ffh_cstate_probe > 2056 microcode_write > 0 acpi_processor_get_throttling > 2048 check_supported_cpu (and most of that is performance-uncritical.) Ingo
next prev parent reply other threads:[~2008-01-18 20:49 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 ` Ingo Molnar [this message] 2008-01-18 20:55 ` [PATCH 4/5] x86: Add config variables for SMP_MAX Mike Travis 2008-01-18 20:58 ` Andi Kleen 2008-01-28 16:45 ` Paul Jackson 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=20080118204845.GD3079@elte.hu \ --to=mingo@elte.hu \ --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=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: linkBe 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).