lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180416140846.0effe6ad@lwn.net>
Date:   Mon, 16 Apr 2018 14:08:46 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Thymo van Beers <thymovanbeers@...il.com>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: kernel-parameters.txt: Fix whitespace

On Mon, 16 Apr 2018 17:45:01 +0200
Thymo van Beers <thymovanbeers@...il.com> wrote:

> Some lines used spaces instead of tabs at line start.
> This can cause mangled lines in editors due to inconsistency.
> 
> Replace spaces for tabs where appropriate.

Seems like a fine idea.  The patch doesn't apply, though; can you please
make a version against current docs-next?  (Or against 4.17-rc1 will work
too).

Also...

>  			domain
> -			  Isolate from the general SMP balancing and scheduling
> -			  algorithms. Note that performing domain isolation this way
> -			  is irreversible: it's not possible to bring back a CPU to
> -			  the domains once isolated through isolcpus. It's strongly
> -			  advised to use cpusets instead to disable scheduler load
> -			  balancing through the "cpuset.sched_load_balance" file.
> -			  It offers a much more flexible interface where CPUs can
> -			  move in and out of an isolated set anytime.
> -
> -			  You can move a process onto or off an "isolated" CPU via
> -			  the CPU affinity syscalls or cpuset.
> -			  <cpu number> begins at 0 and the maximum value is
> -			  "number of CPUs in system - 1".
> +				Isolate from the general SMP balancing and scheduling
> +				algorithms. Note that performing domain isolation this way
> +				is irreversible: it's not possible to bring back a CPU to
> +				the domains once isolated through isolcpus. It's strongly
> +				advised to use cpusets instead to disable scheduler load
> +				balancing through the "cpuset.sched_load_balance" file.
> +				It offers a much more flexible interface where CPUs can
> +				move in and out of an isolated set anytime.
> +
> +			You can move a process onto or off an "isolated" CPU via
> +			the CPU affinity syscalls or cpuset.
> +			<cpu number> begins at 0 and the maximum value is
> +			"number of CPUs in system - 1".

This would appear to have changed the indentation of some of the text?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ