linux-kernel - Re: [RFC v1] Tunable sched_mc_power

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: <87k5gcqpbm.fsf@basil.nowhere.org>
Date:	Thu, 26 Jun 2008 15:49:01 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Linux Kernel <linux-kernel@...r.kernel.org>,
	svaidy@...ux.vnet.ibm.com
Cc:	Suresh B Siddha <suresh.b.siddha@...el.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Dipankar Sarma <dipankar@...ibm.com>,
	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	Vatsa <vatsa@...ux.vnet.ibm.com>,
	Gautham R Shenoy <ego@...ibm.com>
Subject: Re: [RFC v1] Tunable sched_mc_power_savings=n

Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com> writes:
>
> The idea being proposed is to enhance the tunable with varied degrees
> of consolidation that can work best for different workload
> characteristics.  echo 2 > /sys/.../sched_mc_power_savings could
> enable more aggressive consolidation than the default.

It would be better to fix the single power saving default to work
better with bursty workloads too than to add more tunables. Tunables
are basically "we give up, let's push the problem to the user"
which is not nice. I suspect a lot of users won't even know if their
workloads are bursty or not.  Or they might have workloads which
are both bursty and not bursty.

Or did you try that and failed?

-Andi
--
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/