Re: [PATCH] doc: Document the relax_domain_level kernel boot argument

[Li Zefan]

Paul Jackson wrote:
> From: Paul Jackson <pj@xxxxxxx>
> 
> Document the kernel boot parameter: relax_domain_level=.
> 
> Signed-off-by: Paul Jackson <pj@xxxxxxx>
> 
> ---
>  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.
> +
>  This file is per-cpuset and affect the sched domain where the cpuset
>  belongs to.  Therefore if the flag 'sched_load_balance' of a cpuset
>  is disabled, then 'sched_relax_domain_level' have no effect since
> --- 2.6.26-rc5-mm3.orig/Documentation/kernel-parameters.txt	2008-06-27 06:28:26.000000000 -0700
> +++ 2.6.26-rc5-mm3/Documentation/kernel-parameters.txt	2008-06-29 21:51:10.477997208 -0700
> @@ -1732,6 +1732,10 @@ and is between 256 and 4096 characters. 
>  			Format: <reboot_mode>[,<reboot_mode2>[,...]]
>  			See arch/*/kernel/reboot.c or arch/*/kernel/process.c			
>  
> +	relax_domain_level=
> +			[KNL, SMP] Set schedulers default relax_domain_level.
> +			See Documentation/cpusets.txt.
> +

is [KNL,SMP] more consistent ?

and s/schedulers/scheduler's/

but maybe I'm wrong due to my English skill.

>  	reserve=	[KNL,BUGS] Force the kernel to ignore some iomem area
>  
>  	reservetop=	[X86-32]
> 

Reviewed-by: Li Zefan <lizf@xxxxxxxxxxxxxx>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/