From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: 3.9.0 + CONFIG_X86_INTEL_PSTATE=y -> ThinkPad T420 with i5 lost ACPI functionality
Date: Mon, 13 May 2013 10:57:36 -0700 [thread overview]
Message-ID: <51912990.8020206@intel.com> (raw)
In-Reply-To: <519120CC.10403@gmx.de>
On 05/13/2013 10:20 AM, Toralf Förster wrote:
> On 05/13/2013 06:43 PM, Dirk Brandewie wrote:
>> I spent some more time looking for a solution to this you can get same
>> behavior
>> by setting a config option in BOINC "Use at most X % CPU time"
>
> yes - that's true. But BOINC is just an example.
>
> If "nice -19 <loooong running background job" is nowadays so uncommon,
> then I'm just curious what's the modern (easy) way of doing that ?
>
I believe using CGROUP's is the right answer for limiting this type
of load.
I have not tested it but from reading:
Documentation/scheduler/sched-design-CFS.txt
https://wiki.archlinux.org/index.php/Cgroups
You should be able to do something like the following:
cd /sys/fs/cgroup/cpu
mkdir bonic
echo 400 > boinc/cpu.shares
boinc &
echo $! > boinc/tasks
Should limit the boinc group to ~40% of the cpu.
WARNING completely untested YMMV
--Dirk
next prev parent reply other threads:[~2013-05-13 17:57 UTC|newest]
Thread overview: 19+ 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 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
[not found] ` <51842F6F.1050005-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-05-04 7:57 ` Toralf Förster
2013-05-04 7:57 ` Toralf Förster
2013-05-10 13:10 ` Rafael J. Wysocki
2013-05-10 13:10 ` Rafael J. Wysocki
2013-05-13 16:43 ` Dirk Brandewie
2013-05-13 16:43 ` Dirk Brandewie
2013-05-13 17:20 ` Toralf Förster
2013-05-13 17:57 ` Dirk Brandewie [this message]
2013-05-13 19:13 ` Toralf Förster
2013-05-13 19:24 ` Dirk Brandewie
2013-05-13 19:24 ` Dirk Brandewie
2013-05-28 18:11 ` Toralf Förster
2013-07-07 8:44 ` Toralf Förster
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=51912990.8020206@intel.com \
--to=dirk.brandewie@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=toralf.foerster@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.