linux-kernel - Re: [PATCH tip/core/rcu 0/2] Documentation changes for 3.11

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]

Date:	Tue, 21 May 2013 10:33:44 -0700
From:	Josh Triplett <josh@...htriplett.org>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
	dipankar@...ibm.com, akpm@...ux-foundation.org,
	mathieu.desnoyers@...icios.com, niv@...ibm.com, tglx@...utronix.de,
	peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
	dhowells@...hat.com, edumazet@...gle.com, darren@...art.com,
	fweisbec@...il.com, sbw@....edu
Subject: Re: [PATCH tip/core/rcu 0/2] Documentation changes for 3.11

On Mon, May 20, 2013 at 07:49:34AM -0700, Paul E. McKenney wrote:
> Hello!
> 
> A pair of documentation changes.  These are not directly related to RCU,
> but if no one adopts them, I will send them up with the RCU commits.  The
> patches are as follows:
> 
> 1.	Changes to the new Documentation/timers/NO_HZ.txt documentation
> 	based on review comments from Sedat Dilek.
> 
> 2.	Document ways of turning off the scheduling-clock tick even when
> 	there is more than one runnable task on a given CPU.
> 
> 3.	Document ways of avoiding OS jitter form the kworker workqueue
> 	kthreads.

For some reason these are numbered 1/2, 2/2, and 1/1.

In any case, for all three:

Reviewed-by: Josh Triplett <josh@...htriplett.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/