All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nebojsa Trpkovic <trx@inbox.ru>
To: cpufreq@www.linux.org.uk
Subject: Re: [PATCH] Another powernow-k7 patch for Desktop XP-M usage
Date: Thu, 21 Oct 2004 02:56:57 +0200	[thread overview]
Message-ID: <41770959.6060403@inbox.ru> (raw)
In-Reply-To: <20041020094304.GC22405@poupinou.org>

Bruno Ducrot wrote:

>Hi,
>
>On Fri, Oct 15, 2004 at 01:26:43AM +0200, Nebojsa Trpkovic wrote:  
>  
>
>It's a very large latency, preventing to actually making any kind
>of dynamic frequencies really usefull, and since there is no voltage
>scaling, it's IMHO not so usefull for power consuption purpose (though
>this may help for cooling purpose).
>
>  
>

Well, I have only two working states (1GHz and 2.1GHz) that I chage by 
cpudyn. I poll CPU usage once per 500ms because 1GHz Barton is strong 
enough to respond to all my interactive needs without instant switching 
to 2.1GHz. Switching to 2.1GHz is done by some realy huge load 
(compiling gentoo...) and spikes are neutralized.
So, as I calculated, in the worst scenario there can be only 2 frequency 
changes during 1 second, and loosing of ~2ms (~1700ns) per  1 second for 
transition purposes is not so big deal (~0.2% of cpu time).

And, yes, I use it for cooling, but to be cool, too ;)

  parent reply	other threads:[~2004-10-21  0:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12  8:18 [PATCH] Another powernow-k7 patch for Desktop XP-M usage Hendrik Muhs
2004-10-14 23:26 ` Nebojsa Trpkovic
2004-10-20  9:43   ` Bruno Ducrot
2004-10-20 22:05     ` Harald Milz
2004-10-21  0:56     ` Nebojsa Trpkovic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-15  7:05 Hendrik Muhs
2004-10-15 22:28 ` Nebojsa Trpkovic
2004-11-29 21:36   ` Nebojsa Trpkovic
2004-10-16 16:11 ` mark newman
2005-01-14 11:46 ` Jarkko Lavinen
2005-01-17 15:21   ` Hendrik Muhs
2005-01-17 16:31     ` Jarkko Lavinen
2005-01-19 15:35     ` Jarkko Lavinen
2004-12-01 20:09 Hendrik Muhs

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=41770959.6060403@inbox.ru \
    --to=trx@inbox.ru \
    --cc=cpufreq@www.linux.org.uk \
    /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.