linux-kernel - Re: PATCH] cpuidle: A new variant of the menu governor to boost IO performance

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19114.41505.479086.782442@stoffel.org>
Date:	Fri, 11 Sep 2009 15:16:49 -0400
From:	"John Stoffel" <john@...ffel.org>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org, lenb@...nel.org, mingo@...e.hu,
	akpm@...ux-foundation.org, peterz@...radead.org,
	yanmin_zhang@...ux.intel.com, torvalds@...ux-foundation.org,
	jens.axboe@...cle.com
Subject: Re: PATCH] cpuidle: A new variant of the menu governor to boost IO
 performance

>>>>> "Arjan" == Arjan van de Ven <arjan@...radead.org> writes:

Arjan> From: Arjan van de Ven <arjan@...ux.intel.com>
Arjan> Subject: [PATCH] cpuidle: A new variant of the menu governor

Arjan> This patch adds a new idle governor which balances power savings,
Arjan> energy efficiency and performance impact.

Arjan> The reason for a reworked governor is that there have been
Arjan> serious performance issues reported with the existing code
Arjan> on Nehalem server systems.

Arjan> To show this I'm sure Andrew wants to see benchmark results:
Arjan> (benchmark is "fio", "no cstates" is using "idle=poll")

Arjan> 		no cstates	current linux	new algorithm
Arjan> 1 disk		107 Mb/s	85 Mb/s		105 Mb/s
Arjan> 2 disks		215 Mb/s	123 Mb/s	209 Mb/s
Arjan> 12 disks	590 Mb/s	320 Mb/s	585 Mb/s

Don't you need another row or three where you show a) how much time
each test took, and b) how much (or average) power used for the
duration of the test?  

I'm just curious if the new algorithm (or even the current one!) saves
any appreciable power over the 'no cstates' case.  It's not clear what
the savings are.  

Also, latency in terms of switching to higher power and then back down
would be nice to see.

Cheers,
John
--
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/