public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Alexander Clouter <alex@digriz.org.uk>
Cc: cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org,
	venkatesh.pallipadi@intel.com, linux@dominikbrodowski.de
Subject: Re: [patch 1/4] cpufreq_conservative: update and align of codebase
Date: Wed, 22 Mar 2006 01:22:10 -0800	[thread overview]
Message-ID: <20060322012210.1c0fb11f.akpm@osdl.org> (raw)
In-Reply-To: <20060322085807.GA10689@inskipp.digriz.org.uk>

Alexander Clouter <alex@digriz.org.uk> wrote:
>
> *NEW* patches, for kernel 2.6.16
> 
>  Something I had been meaning to do for a while.  The codebases between
>  ondemand and conservative have strayed and as Venkatesh has far more Clue(tm)
>  than I am going to adjust my code to look more like his :)
> 
>  Another reason to do this is ages ago, knowingly, I did a piss poor attempt
>  at making conservative less responsive by knocking up
>  DEF_SAMPLING_RATE_LATENCY_MULTIPLIER by two orders of magnitude.  I did fix
>  this ages ago but in my dis-organisation I must have toasted the diff and
>  left it the way it was.  About two weeks ago a user contacted me saying he
>  was having problems with the conservative governor with his AMD Athlon XP-M
>  2800+ as /sys/devices/system/cpu/cpu0/cpufreq/conservative showed
>    sampling_rate_min   9950000
>    sampling_rate_max   1360065408
> 
>  Nine seconds to decide about changing the frequency....not too responsive :)

umm, that's not really a changelog.  Please, see
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt.  Section 2a is
relevant too..

Thanks.

      reply	other threads:[~2006-03-22  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22  8:58 [patch 1/4] cpufreq_conservative: update and align of codebase Alexander Clouter
2006-03-22  9:22 ` Andrew Morton [this message]

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=20060322012210.1c0fb11f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=alex@digriz.org.uk \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.de \
    --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