From: Li Zefan <lizf@cn.fujitsu.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: Paul Jackson <pj@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lee.Schermerhorn@hp.com, linux-kernel@vger.kernel.org,
Michael Kerrisk <mtk.manpages@googlemail.com>,
rientjes@google.com
Subject: Re: [PATCH] doc: Document the relax_domain_level kernel boot argument
Date: Mon, 30 Jun 2008 15:14:51 +0800 [thread overview]
Message-ID: <486887EB.5090304@cn.fujitsu.com> (raw)
In-Reply-To: <486883D0.8070409@jp.fujitsu.com>
Hidetoshi Seto wrote:
> Hi Paul,
>
> Paul Jackson wrote:
>> From: Paul Jackson <pj@sgi.com>
>>
>> Document the kernel boot parameter: relax_domain_level=.
>>
>> Signed-off-by: Paul Jackson <pj@sgi.com>
>>
>> ---
>> Documentation/cpusets.txt | 3 +++
>> Documentation/kernel-parameters.txt | 4 ++++
>> 2 files changed, 7 insertions(+)
>>
>> --- 2.6.26-rc5-mm3.orig/Documentation/cpusets.txt 2008-06-27 06:55:34.000000000 -0700
>> +++ 2.6.26-rc5-mm3/Documentation/cpusets.txt 2008-06-29 21:49:53.984674621 -0700
>> @@ -546,6 +546,9 @@ otherwise initial value -1 that indicate
>> ( 4 : search nodes in a chunk of node [on NUMA system] )
>> ( 5~ : search system wide [on NUMA system])
>>
>> +The system default is 0 (no search). The system default can be
>> +changed using the relax_domain_level= boot parameter.
>
> The system default is architecture dependent. You can change your
> system's default using the relax_domain_level= boot parameter.
>
but the system default is 0 by default. and 0 means no search no matter
what architecture is. ;)
> Thanks,
> H.Seto
>
>
next prev parent reply other threads:[~2008-06-30 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 4:56 [PATCH] doc: Document the relax_domain_level kernel boot argument Paul Jackson
2008-06-30 6:08 ` Li Zefan
2008-06-30 7:10 ` Michael Kerrisk
2008-06-30 13:01 ` Paul Jackson
2008-06-30 6:57 ` Hidetoshi Seto
2008-06-30 7:14 ` Li Zefan [this message]
2008-06-30 7:40 ` Hidetoshi Seto
2008-06-30 7:44 ` Li Zefan
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=486887EB.5090304@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.com \
--cc=pj@sgi.com \
--cc=rientjes@google.com \
--cc=seto.hidetoshi@jp.fujitsu.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