All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] x86: add percpu, cpu_to_node debug options
Date: Thu, 24 Jan 2008 08:24:54 -0800	[thread overview]
Message-ID: <4798BBD6.1020704@sgi.com> (raw)
In-Reply-To: <20080124155938.GC4857@elte.hu>

Ingo Molnar wrote:
> * travis@sgi.com <travis@sgi.com> wrote:
> 
>> +config THREAD_ORDER
>> +	int "Kernel stack size (in page order)"
>> +	range 1 3
>> +	depends on X86_64
>> +	default "3" if X86_SMP
>> +	default "1"
>> +	help
>> +	  Increases kernel stack size.
> 
> you keep sending this broken portion, please dont ... 
> 
> 	Ingo

Sorry, I noted in the comments that that's only for the DEBUG patch, and
you shouldn't apply that, except when attempting to up the NR_CPUS count
for testing.  (I should perhaps just quit submitting it? ;-)

As a side note, soon we should be able to up NR_CPUS and not worry about
stack overflows.

Thanks,
Mike

WARNING: multiple messages have this Message-ID (diff)
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] x86: add percpu, cpu_to_node debug options
Date: Thu, 24 Jan 2008 08:24:54 -0800	[thread overview]
Message-ID: <4798BBD6.1020704@sgi.com> (raw)
In-Reply-To: <20080124155938.GC4857@elte.hu>

Ingo Molnar wrote:
> * travis@sgi.com <travis@sgi.com> wrote:
> 
>> +config THREAD_ORDER
>> +	int "Kernel stack size (in page order)"
>> +	range 1 3
>> +	depends on X86_64
>> +	default "3" if X86_SMP
>> +	default "1"
>> +	help
>> +	  Increases kernel stack size.
> 
> you keep sending this broken portion, please dont ... 
> 
> 	Ingo

Sorry, I noted in the comments that that's only for the DEBUG patch, and
you shouldn't apply that, except when attempting to up the NR_CPUS count
for testing.  (I should perhaps just quit submitting it? ;-)

As a side note, soon we should be able to up NR_CPUS and not worry about
stack overflows.

Thanks,
Mike

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-01-24 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 23:04 [PATCH 0/3] x86/non-x86: percpu, node ids, apic ids x86.git fixup travis
2008-01-22 23:04 ` travis
2008-01-22 23:04 ` [PATCH 1/3] x86: fix percpu, nodeids, apicids in x86.git travis
2008-01-22 23:04   ` travis
2008-01-22 23:04 ` [PATCH 2/3] x86: add percpu, cpu_to_node debug options travis
2008-01-22 23:04   ` travis
2008-01-24 15:59   ` Ingo Molnar
2008-01-24 15:59     ` Ingo Molnar
2008-01-24 16:24     ` Mike Travis [this message]
2008-01-24 16:24       ` Mike Travis
2008-01-22 23:04 ` [PATCH 3/3] generic: fixup percpu Kconfig options, fold percpu_modcopy into module.c travis
2008-01-22 23:04   ` travis
2008-01-22 23:04   ` travis

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=4798BBD6.1020704@sgi.com \
    --to=travis@sgi.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    /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.