public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
	linux-kernel@vger.kernel.org, tuukka.tikkanen@elektrobit.com,
	ck@vds.kolivas.org
Subject: Re: [patch] i386 dynamic ticks 2.6.13-rc4 (code reordered)
Date: Tue, 2 Aug 2005 22:04:04 +1000	[thread overview]
Message-ID: <200508022204.05562.kernel@kolivas.org> (raw)
In-Reply-To: <20050802113137.GK15903@atomide.com>

On Tue, 2 Aug 2005 21:31, Tony Lindgren wrote:
> * Con Kolivas <kernel@kolivas.org> [050802 03:54]:
>
> > I need to ask you why you think limiting the maximum Hz is a bad idea? On
> > a laptop, say we have set the powersave governor, we have already told
> > the kernel we are interested in maximising power saving at the expense of
> > performance. Would it not be appropriate for this to be linked in a way
> > that sets maximum Hz to some value that maximises power save (whatever
> > that value is) at that time?
>
> With dyntick the system will run at max HZ only when busy. It is possible
> that cutting down max HZ might cause some savings while busy, but I would
> assume the savings are minimal.
>
> I personally prefer to have the performance available when needed, and
> max savings while idle.

That's what I felt too but wasn't sure about the power saving. However what 
you say makes complete sense; if the machine is loaded then the extra power 
overhead of 1000 vs 100 ticks is meaningless, but throughput may be of 
concern. However I managed to get it booted on my p4 at home and while I'm 
using it under load I find it rarely gets to 1000Hz during realistic loads. 
I'll be posting a fresh patch shortly with the last few cleanups I could 
find, that I'm now running on 2.6.13-rc5.

Cheers,
Con

  reply	other threads:[~2005-08-02 12:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02  4:43 [patch] i386 dynamic ticks 2.6.13-rc4 (code reordered) Con Kolivas
2005-08-02  5:35 ` [ck] " Michael Marineau
2005-08-02  5:49 ` Con Kolivas
2005-08-02  5:52   ` Lee Revell
2005-08-02  5:56     ` Con Kolivas
2005-08-02  6:24       ` Lee Revell
2005-08-02  7:17         ` Tony Lindgren
2005-08-02  7:39           ` Con Kolivas
2005-08-02  8:15             ` Tony Lindgren
2005-08-02 10:54               ` Con Kolivas
2005-08-02 11:31                 ` Tony Lindgren
2005-08-02 12:04                   ` Con Kolivas [this message]
2005-08-02  7:21 ` Tony Lindgren
2005-08-02 14:01 ` Avuton Olrich
2005-08-02 14:05   ` Con Kolivas
2005-08-06 14:54 ` Theodore Ts'o
2005-08-06 15:00   ` Con Kolivas
2005-08-08  5:43     ` Stefan Seyfried
2005-08-08 21:54     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-08-08 18:37 Pallipadi, Venkatesh
2005-08-10  6:44 ` Thomas Renninger
2005-08-10  6:57   ` Con Kolivas

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=200508022204.05562.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --cc=tony@atomide.com \
    --cc=tuukka.tikkanen@elektrobit.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