public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Dirk Brandewie <dirk.brandewie@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.9.0 + CONFIG_X86_INTEL_PSTATE=y  -> ThinkPad T420 with i5 lost ACPI functionality
Date: Sun, 07 Jul 2013 10:44:41 +0200	[thread overview]
Message-ID: <51D92A79.2030609@gmx.de> (raw)
In-Reply-To: <51A4F363.2040003@gmx.de>

On 05/28/2013 08:11 PM, Toralf Förster wrote:
> cgexec from the libcgroup-tools package (fedora name) look like it will
>> place
>> a process in a group for you.
>> 
>> https://wiki.archlinux.org/index.php/Cgroups
>> 
>> Has some useful examples.
>> 
>> --Dirk
>> 

What I'm looking for is a command telling the governor "do not increase
CPU frequency for this process (group)" - because that's the main
intention of "nice -19", right ?

Without such a simple-to-use-command/replacement-of-nice-19 a lot of
systems in the wild won't work as expected with the p-state driver in
place of acpi_cpufreq.

(And AFAICR this was one of those reasons why for ondemand the
"ignore_nice" sysfs feature was implemented)

Especially RedHat systems using the  kernel-ml will automatically switch
to p-state - pretty sure, that's not wanted by a reasonable amount of
people, or ?

-- 
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

      reply	other threads:[~2013-07-07  8:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 16:55 3.9.0 + CONFIG_X86_INTEL_PSTATE=y -> ThinkPad T420 with i5 lost ACPI functionality Toralf Förster
2013-05-03 19:36 ` Rafael J. Wysocki
2013-05-03 21:10   ` Dirk Brandewie
2013-05-03 21:26     ` Toralf Förster
2013-05-03 21:43       ` Dirk Brandewie
2013-05-04  7:57         ` Toralf Förster
2013-05-10 13:10           ` Rafael J. Wysocki
2013-05-13 16:43   ` Dirk Brandewie
2013-05-13 17:20     ` Toralf Förster
2013-05-13 17:57       ` Dirk Brandewie
2013-05-13 19:13         ` Toralf Förster
2013-05-13 19:24           ` Dirk Brandewie
2013-05-28 18:11             ` Toralf Förster
2013-07-07  8:44               ` Toralf Förster [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51D92A79.2030609@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=dirk.brandewie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox