On 9/7/18 2:40 PM, Jan H. Schönherr wrote:
> Add a new command line argument cosched_max_level=<n>, which allows
> enabling coscheduling at boot. The number corresponds to the scheduling
> domain up to which coscheduling can later be enabled for cgroups.
>
> For example, to enable coscheduling of cgroups at SMT level, one would
> specify cosched_max_level=1.
>
> The use of symbolic names (like off, core, socket, system) is currently
> not possible, but could be added. However, to force coscheduling at up
> to system level not knowing the scheduling domain topology in advance,
> it is possible to just specify a too large number. It will be clamped
> transparently to system level.
>
> Signed-off-by: Jan H. Schönherr <jscho...@amazon.de>
> ---
> kernel/sched/cosched.c | 32 +++++++++++++++++++++++++++++++-
> 1 file changed, 31 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/sched/cosched.c b/kernel/sched/cosched.c
> index eb6a6a61521e..a1f0d3a7b02a 100644
> --- a/kernel/sched/cosched.c
> +++ b/kernel/sched/cosched.c
> @@ -162,6 +162,29 @@ static int __init cosched_split_domains_setup(char *str)
>
> early_param("cosched_split_domains", cosched_split_domains_setup);
>
> +
> +early_param("cosched_max_level", cosched_max_level_setup);
> +
Hi,
Please document both of these kernel parameters in
Documentation/admin-guide/kernel-parameters.txt.
thanks,
--
~Randy
