public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <lkml@kcore.org>
To: Eric Piel <Eric.Piel@tremplin-utc.net>
Cc: linux-kernel@vger.kernel.org, cpufreq@zenii.linux.org.uk,
	davej@redhat.com, linux@dominikbrodowski.net
Subject: Re: cpufreq on-demand governor up_treshold?
Date: Mon, 14 Mar 2005 13:40:58 +0100	[thread overview]
Message-ID: <200503141340.59714.lkml@kcore.org> (raw)
In-Reply-To: <42354400.7070500@tremplin-utc.net>

On Monday 14 March 2005 08:57, Eric Piel wrote:
> Jan De Luyck a écrit :
> > Hello lists,
> >
> > (please cc me from cpufreq list)
> >
> > I've since yesterday started using the ondemand governor. Seems to work
> > fine, tho I can't seem to find a reason why it keeps scaling my processor
> > speed upwards tho the processor use never exceeds 30% (been watching top
> > -d 1).
> >
> >
> > Any hints?
>
> You can try the three attached patches in the order :
> ondemand-cleanup-factorise-idle-measurement-2.6.11.patch
> ondemand-save-idle-up-for-all-cpu-2.6.11.patch
> ondemand-automatic-downscaling-2.6.11-accepted.patch
>
> They are available on the cpufreq list but as it's difficult to access
> it I'm sending them again, all together. These are the last things that
> Venki and I have been working on. It should solve your problem
> (actually, only the last patch, but it depends on the two previous
> patches). Please, let me know if it works.

Okay, now the behaviour of the ondemand governor looks more 'sane'. Thanks, it 
looks like a huge improvement :)

Jan

-- 
Snow and adolescence are the only problems that disappear if you ignore
them long enough.

  parent reply	other threads:[~2005-03-14 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14  7:29 cpufreq on-demand governor up_treshold? Jan De Luyck
2005-03-14  7:57 ` Eric Piel
2005-03-14 11:19   ` Bruno Ducrot
2005-03-14 12:40   ` Jan De Luyck [this message]
2005-03-14 22:39   ` Dominik Brodowski
2005-05-11  1:33   ` Dave Jones

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=200503141340.59714.lkml@kcore.org \
    --to=lkml@kcore.org \
    --cc=Eric.Piel@tremplin-utc.net \
    --cc=cpufreq@zenii.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /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