public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, "Pallipadi,
	Venkatesh" <venkatesh.pallipadi@intel.com>,
	Jonathan Corbet <corbet@lwn.net>, Pavel Machek <pavel@ucw.cz>,
	Bernard Blackham <b-lkml@blackham.com.au>,
	Christian Hesse <mail@earthworm.de>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Thomas Renninger <trenn@suse.de>
Subject: Re: [PATCH] Dynamic tick for x86 version 050609-2
Date: Mon, 13 Jun 2005 08:25:07 -0700	[thread overview]
Message-ID: <20050613152507.GB7862@atomide.com> (raw)
In-Reply-To: <200506130454.j5D4suNY006032@turing-police.cc.vt.edu>

* Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> [050612 21:55]:
> On Thu, 09 Jun 2005 21:30:18 PDT, Tony Lindgren said:
> 
> > Thanks for all the comments. Here's an updated dyntick patch.
> 
> Patches with 3 minor rejects against -rc6-mm1, boots, and seems to work well on
> my Dell Latitude C840 laptop - although running at full load with seti@home
> causes the expected 250 timer ticks/sec, running a mostly-idle  X session only
> gets about 117, and having xmms and a few other things running it hits about
> 170 tics/sec. I've had the CPU speed bounce between 1.2G and 1.6G a few times
> and it didn't seem to blink either. Even NTP is happy with what it sees.. ;)

Cool.

> Need to rebuild with CONFIG_HZ=1000 and see what it does, and see what it does
> to actual power consumption.

You may also want to check out the patch by Thomas Renninger for ACPI
C-states. I've added a link to it at:

http://muru.com/dyntick/

> Minor nit:  The implementation of /sys/devices/system/timer/timer0/dyn_tick_state
> violates the one-value-per-file rule for sysfs.  I suspect this needs to
> become a directory with 3-4 files in it, each containing one value.

Yeah, I'll clean up that for the next version.

Tony

  reply	other threads:[~2005-06-13 15:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 22:14 [PATCH] Dynamic tick for x86 version 050602-1 Pallipadi, Venkatesh
2005-06-09  1:40 ` Tony Lindgren
2005-06-10  4:30   ` [PATCH] Dynamic tick for x86 version 050609-2 Tony Lindgren
2005-06-10  9:10     ` Pavel Machek
2005-06-10 15:10       ` Tony Lindgren
2005-06-13  4:54     ` Valdis.Kletnieks
2005-06-13 15:25       ` Tony Lindgren [this message]
2005-06-13 16:47         ` Valdis.Kletnieks
2005-06-13 18:01           ` Thomas Renninger
2005-06-13 18:22             ` Tony Lindgren
2005-06-13 19:07             ` Valdis.Kletnieks
2005-06-14  9:39               ` Thomas Renninger
2005-06-14 15:40                 ` Valdis.Kletnieks
2005-06-13 17:09     ` Srivatsa Vaddagiri
2005-06-13 17:55       ` Andi Kleen
2005-06-13 18:37         ` Tony Lindgren
2005-06-13 18:51           ` Andi Kleen
2005-06-13 19:35             ` Tony Lindgren
2005-06-13 19:48             ` Valdis.Kletnieks
2005-06-13 18:27       ` Tony Lindgren

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=20050613152507.GB7862@atomide.com \
    --to=tony@atomide.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=b-lkml@blackham.com.au \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@earthworm.de \
    --cc=pavel@ucw.cz \
    --cc=trenn@suse.de \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=zwane@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox