public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: joni@shade-fx.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: ondemand ignore_nice_level
Date: Mon, 8 Aug 2011 17:10:21 -0400	[thread overview]
Message-ID: <20110808211021.GA12293@redhat.com> (raw)
In-Reply-To: <4e403bd4.5YAAoSWMDWtU5KOP%joni@shade-fx.com>

On Mon, Aug 08, 2011 at 10:41:08PM +0300, joni@shade-fx.com wrote:
 
 > This patch add functionality for cpufreq ondemand where user can decide
 > what nice level will be ignored when ondemand governors ignore_nice_load 
 > is used. The patch introduces new file ignore_nice_level where nice level can 
 > be tuned. In other words, user can select processes which can raise cpu
 > speed by setting processes to certain nice level and tuning ignore level
 > via ignore_nice_level at /sys/devices/system/cpu/cpufreq/ondemand .
 > 
 > To achieve this, the patch add a new nicevalue[40] array for cpu_usage_stat
 > struct where it keeps cpu usage statistic for each nice value.
 > This patch also makes this array visible for user via /proc/stat .
 > /proc/stat file gets a couple of new lines which corresponds used cpu time
 > for each nice level and for each cpu core.
 
I'm reluctant to add yet another set of knobs to tweak unless it's something that
people are really going to use. 

If there's a real use-case for this, that ignore_nice_load doesn't already provide,
I could be swayed, but I'm not really seeing it.

	Dave


  reply	other threads:[~2011-08-08 21:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 19:41 [PATCH] cpufreq: ondemand ignore_nice_level joni
2011-08-08 21:10 ` Dave Jones [this message]
2011-08-09 10:12 ` Peter Zijlstra
2011-08-09 17:14   ` Joni Martikainen

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=20110808211021.GA12293@redhat.com \
    --to=davej@redhat.com \
    --cc=joni@shade-fx.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