linux-kernel - Re: [PATCH 2/3] sched: idle: Add sched balance option

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:	Sat, 26 Apr 2014 08:17:44 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Amit Kucheria <amit.kucheria@...aro.org>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Ingo Molnar <mingo@...e.hu>,
	Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] sched: idle: Add sched balance option


* Rafael J. Wysocki <rjw@...ysocki.net> wrote:

> > > Well, so now the question is whether or not we relly want to 
> > > always go to the "power" (or "energy efficiency" if you will) 
> > > mode if the system is on battery.  That arguably may not be a 
> > > good thing even for energy efficiency depending on how exactly 
> > > the modes are defined.
> > 
> > Nobody is talking about always. But in general it seems a good 
> > enough approach. Hell, many of the AC/BAT switches in todays power 
> > management crap things are not always right.
> > 
> > Do I want it to dim the LCD further when I unplug the laptop -- 
> > mostly no, but still it does. And the most annoying one is that it 
> > reduces the screen blank time to something near 5 seconds or so.
> > 
> > Why would this be any different?
> 
> And why do we have to do things that we hate it when they are done 
> by others?

He replied to your question of 'do we want to act on power events'.

The answer is: yes, from the scheduler point of view we want to act on 
power events by default, and if a user does not want that default 
behavior, it's not an unprecedented request and GUIs offer various 
ways to tweak screen dimming and other power saving details.

So "trying to save power" is the default everywhere, and the scheduler 
wants to do the same. The main reason we couldn't do this before was 
that the scheduler's 'power saving mode' was dysfunctional. That is 
being fixed.

So lets try this, it's high time.

Thanks,

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