All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@zenii.linux.org.uk,
	Alexander Clouter <alex-kernel@digriz.org.uk>,
	linux@dominikbrodowski.net
Subject: Re: cpufreq on-demand governor up_treshold?
Date: Fri, 13 May 2005 01:16:03 +0200	[thread overview]
Message-ID: <4283E3B3.3070501@tremplin-utc.net> (raw)
In-Reply-To: <4281F837.5070608@tremplin-utc.net>

Eric Piel a écrit :
> Dave Jones a écrit :
> 
>> On Tue, May 10, 2005 at 09:33:34PM -0400, Dave Jones wrote:
>>  >  > I'm preparing the first cpufreq->linus sync right now.
>>  > Can you write up some descriptions & signed-off-by: lines for
>>  > these three please ?
>>
>> Additionally, it'll need tweaking to diff on top of whats
>> currently in the pending queue. looks like the patch at
>> http://www.codemonkey.org.uk/projects/cpufreq/pending-patches/CPUFREQ-04-ondemand-cleanups.patch 
>>
>> upsets yours a little.
>>
> Here follows the three patches, updated for the last snapshot of 
> cpufreq. I knew there was a conflict (CPUFREQ-04 is also a patch I wrote 
> ;-) ) but was too lasy to resend them. Here you are!
> 
Hi Dave,

I've just noticed that while I was rediffiing the patches, you had 
integrated the 3 patches of Alexander for the ondemand governor... which 
conflict with mine!

Concerning CPUFREQ-17-ondemand-ignore-nice.patch, it'll just require 
rediffing again my patches, that's easy.

CPUFREQ-18-ondemand-check-rate-and-break-out.patch is in part also 
available in "automatic-downscaling". I hadn't integrated the break if 
the cpu frequency is max because it seemed that resetting the values for 
down frequency is necessary all the time (maybe Venki can confirm?). So 
I would recommand discarding it and just using "automatic-downscaling".

Finally, CPUFREQ-19-ondemand-sys_freq_step.patch brings a feature which 
is probably not needed anymore if you use the "automatic downscaling" 
(this can be argued though). I'd discard it too.

Please, let me know what you are planning to do. If you agree I can 
simply send you my 3 patches against the 20050511 tree minus CPUFREQ-18 
and CPUFREQ-19. IMHO, this would put the ondemand governor in the best 
shape.

Eric

  parent reply	other threads:[~2005-05-12 23:16 UTC|newest]

Thread overview: 19+ 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  7:57   ` Eric Piel
2005-03-14 11:19   ` Bruno Ducrot
2005-03-14 11:19     ` Bruno Ducrot
2005-03-14 12:40   ` Jan De Luyck
2005-03-14 12:40     ` Jan De Luyck
2005-03-14 22:39   ` Dominik Brodowski
2005-03-14 22:39     ` Dominik Brodowski
2005-05-11  1:33   ` Dave Jones
2005-05-11  1:33     ` Dave Jones
2005-05-11  2:34     ` Dave Jones
2005-05-11 12:19       ` Eric Piel
2005-05-11 12:23         ` [PATCH] [1/3] ondemand governor clean-up Eric Piel
2005-05-11 12:27         ` [PATCH][2/3] ondemand governor store the idle ticks for all cpus Eric Piel
2005-05-11 12:31         ` [PATCH][3/3] ondemand governor automatic downscaling Eric Piel
2005-05-12 23:16         ` Eric Piel [this message]
2005-05-17  0:15           ` [PATCH] ondemand,conservative minor bug-fix and cleanup Venkatesh Pallipadi
  -- strict thread matches above, loose matches on Subject: below --
2005-05-11 16:00 cpufreq on-demand governor up_treshold? Pallipadi, Venkatesh

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=4283E3B3.3070501@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=alex-kernel@digriz.org.uk \
    --cc=cpufreq@zenii.linux.org.uk \
    --cc=davej@redhat.com \
    --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 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.