All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Dominik Brodowski <linux@brodo.de>, Dave Jones <davej@redhat.com>
Cc: Ducrot Bruno <ducrot@poupinou.org>, cpufreq@www.linux.org.uk
Subject: RE: [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds
Date: Tue, 11 Nov 2003 11:57:23 -0800	[thread overview]
Message-ID: <88056F38E9E48644A0F562A38C64FB60077A19@scsmsx403.sc.intel.com> (raw)



> -----Original Message-----
> From: cpufreq-bounces@www.linux.org.uk 
> [mailto:cpufreq-bounces@www.linux.org.uk] On Behalf Of 
> Dominik Brodowski
> Sent: Tuesday, November 11, 2003 10:54 AM
> To: Dave Jones
> Cc: Ducrot Bruno; cpufreq@www.linux.org.uk
> Subject: Re: [PATCH][DOCUMENTATION BUGFIX] latency in micro-, 
> not nanoseconds
> 
> 
> On Mon, Nov 10, 2003 at 09:16:54PM +0000, Dave Jones wrote:
> > Ok, I can buy that. But it's not being used at all right 
> now, right ?
> 
> It is used in the ondemand governor already. Venkatesh knows of the
> documentation bug and of the powernow-k7 bug, though.


Yes. Current version of ondemand governor is using the transiton 
latency to decide whether this policy can be enabled on this CPU 
or not. As it does frequent sampling (default - 4 times per sec)
which may not work well you have higher transition latencies. 
I am planning to use transition latency to decide on an 
appropriate sampling frequency for that CPU, in next release 
of ondemand governor, so that the governor can support wider 
range of CPUs (although with different sampling frequencies).


Thanks,
-Venkatesh

             reply	other threads:[~2003-11-11 19:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-11 19:57 Pallipadi, Venkatesh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-04 16:08 [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds Dominik Brodowski
2003-11-10 16:32 ` Dave Jones
2003-11-10 17:15   ` Ducrot Bruno
2003-11-10 17:22     ` Dave Jones
2003-11-10 20:50       ` Dominik Brodowski
2003-11-10 21:16         ` Dave Jones
2003-11-11 18:54           ` Dominik Brodowski
2003-11-11 22:45             ` Dave Jones
2003-11-12 11:01               ` Ducrot Bruno
2003-11-12 14:17                 ` Dave Jones
2003-11-12 15:02                   ` Ducrot Bruno

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=88056F38E9E48644A0F562A38C64FB60077A19@scsmsx403.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=ducrot@poupinou.org \
    --cc=linux@brodo.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.