linux-kernel - Re: A few questions and issues with dynticks, NOHZ and powertop

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:	Mon, 5 Apr 2010 13:34:41 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
Cc:	david@...g.hm, Dominik Brodowski <linux@...inikbrodowski.net>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Dmitry Torokhov <dtor@...l.ru>
Subject: Re: A few questions and issues with dynticks, NOHZ and powertop

On Mon, Apr 05, 2010 at 12:48:59PM -0700, Arjan van de Ven wrote:
> On 4/5/2010 11:44, david@...g.hm wrote:
> >On Mon, 5 Apr 2010, Arjan van de Ven wrote:
> >
> >>On 4/5/2010 8:14, Paul E. McKenney wrote:
> >>>So the main issue is that for many workloads, it is best to run full
> >>>bore
> >>>and get done quickly, thus allowing the entire machine to be powered
> >>>down?
> >>
> >>yep
> >
> >Race To Idle works extremely well in a batch type situation where there
> >is not going to be any work to do after you finish what you have.
> >
> >It doesn't work quite as well if you are going to have new work to do in
> >the near future.
> >
> >You cannot power down the entire machine if you have to look for user
> >input.
> >
> >It takes time (and power) to shut down and start back up, if you are
> >going to have more work to do before you can make the complete cycle
> >(and save more power than it costs to make the transitions), it's best
> >to stay at full power, even if you are idle.
> 
> for the things we're talking about here (memory controllers etc) we're talking
> about single to low double digit microseconds (or even less) of time to go up and down.
> Many of the things you talk about are in the millisecond timeframe.

So the decision will depend not only on the workload itself, but also
on the hardware that the workload uses.

							Thanx, Paul
--
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/