public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: cpufreq@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com
Subject: cpufreq on demand governor sampling rate restricted to HZ even on NO_HZ kernels
Date: Fri, 30 Jan 2009 15:59:13 +0100	[thread overview]
Message-ID: <200901301559.15170.trenn@suse.de> (raw)

Hi,

depending on HZ set to:

100
250
1000

the ondemand governor is currently limited to poll the CPU load
and adjust the frequency (sampling rate sysfs variable) every:

200ms
80ms
20ms

This limitation does not consider NO_HZ which looks wrong?
If this is correct, can someone give me a pointer, I'd like
to understand why.

If NO_HZ can/should go down to 20ms polling and more (current
CPUs are able to switch fast enough, so that the ondemand governor
would calculate the default polling interval below 80ms for them),
this would hurt in respect of C-states at some point.

For performance reasons, one wants to poll as much as possible, for
powersaving reasons (C-states), one wants to poll as seldom as
possible.

I wonder whether it makes sense to dynamically adjust the polling
interval (e.g. by a hint (and initial wakeup) from the scheduler or
taking C-states into account) to:
  - increase the sampling rate, e.g. based on context switching
    activity
  - lower sampling rate when the system is idle (to gain
    full C-state efficiency)
Or in what other way deep C-states could be taken into account
in respect of ondemand polling?

Thanks,

     Thomas


             reply	other threads:[~2009-01-30 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 14:59 Thomas Renninger [this message]
2009-01-30 17:28 ` cpufreq on demand governor sampling rate restricted to HZ even on NO_HZ kernels Pallipadi, Venkatesh
2009-02-03 17:04   ` Thomas Renninger

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=200901301559.15170.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /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