linux-kernel - Re: [ANNOUNCE] 3.8-rc6-nohz4

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: <CAFTL4hyALkyoG640cyPfBG8ym_MeYWfje4oG4966pmXJhickZA@mail.gmail.com>
Date:	Thu, 7 Feb 2013 18:45:04 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Alessio Igor Bogani <abogani@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Chris Metcalf <cmetcalf@...era.com>,
	Christoph Lameter <cl@...ux.com>,
	Geoff Levand <geoff@...radead.org>,
	Gilad Ben Yossef <gilad@...yossef.com>,
	Hakan Akkan <hakanakkan@...il.com>,
	Li Zhong <zhong@...ux.vnet.ibm.com>,
	Namhyung Kim <namhyung.kim@....com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] 3.8-rc6-nohz4

2013/2/7 Steven Rostedt <rostedt@...dmis.org>:
> On Thu, 2013-02-07 at 17:45 +0100, Frederic Weisbecker wrote:
>
>> >
>> > config NO_HZ_TASK
>> >         bool "Stop tick on specified CPUs when single task is running"
>> >         default n
>> >         depends on NO_HZ
>>
>> Ok I launched another debate about that single task thing. I wish we
>> don't make it a fundamental component but rather an implementation
>> detail that can be dynamically dealt with in the future.
>
> It's not just an implementation detail, as it is very visible to the
> user. If they want to take advantage of a task NO_HZ they have to go
> through a bit of loops to make sure only a single task is running on a
> CPU. We should be broadcasting this requirement to educate the users on
> exactly how they can take advantage of this feature.

If you guys really insist I can make it CONFIG_NO_HZ_SINGLETASK. I
don't mind that much. Then when we support hrtick we can rename it to
NO_HZ_FULL or whatever.
--
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/