public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: cpufreq@vger.kernel.org
Cc: Linux PM list <linux-pm@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: does niced processes scales frequency too at the ondemand governor ?
Date: Wed, 06 Nov 2013 19:29:18 +0100	[thread overview]
Message-ID: <527A8A7E.1050906@gmx.de> (raw)

Running a Gentoo Linux at a 4-core CPU (i5) I realize, that compiling
packages using -j4 usually needs twice as long, if I run 4 BOINC
processes in the back ground (nice -n 19) too. Even considering effects
of invalidation of cache data this seems a too big impact in my eyes.

It looks for me like that the BOINC processes scales down the frequency,
when they are running. This behaviour however would be wrong IMO. The
frequency should be scaled just by the non-niced foreground processes,
right ?

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

                 reply	other threads:[~2013-11-06 18:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=527A8A7E.1050906@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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