From: mark gross <mgross@linux.intel.com>
To: Thomas Gleixner <tglx@timesys.com>
Cc: Con Kolivas <kernel@kolivas.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, john stultz <johnstul@us.ibm.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ
Date: Mon, 19 Jun 2006 14:58:22 -0700 [thread overview]
Message-ID: <20060619215822.GA4178@linux.intel.com> (raw)
In-Reply-To: <1150720304.27073.70.camel@localhost.localdomain>
On Mon, Jun 19, 2006 at 02:31:44PM +0200, Thomas Gleixner wrote:
> On Mon, 2006-06-19 at 22:09 +1000, Con Kolivas wrote:
> > Also suffers from:
> > WARNING: "timespec_to_jiffies" [fs/fuse/fuse.ko] undefined!
> >
> > Here is a fix
>
> Doh, where is the brown paperbag shop ?
>
> Thanks, applied.
>
> New queue:
>
> http://www.tglx.de/projects/hrtimers/2.6.17/patch-2.6.17-hrt-dyntick3.patch
>
> http://www.tglx.de/projects/hrtimers/2.6.17/patch-2.6.17-hrt-dyntick3.patches.tar.bz2
>
I'm just giving this a test spin now on my desktop boot. looking at uptime and cat /proc/interrupts
~/work> uptime;cat /proc/interrupts
2:51pm up 0:28, 5 users, load average: 0.00, 0.02, 0.08
CPU0
0: 80007 XT-PIC timer
1: 1776 XT-PIC i8042
2: 0 XT-PIC cascade
8: 2 XT-PIC rtc
9: 0 XT-PIC acpi
11: 2156 XT-PIC eth0
12: 2879 XT-PIC i8042
14: 20402 XT-PIC ide0
15: 11 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
or about 47.6 timer's a second.
This system is mostly idle, is this about right or should I expect even fewer timer ticks?
Is there a way to see timer stats?
FWIW Its nice to see this stuff start getting real.
thanks
--mgross
next prev parent reply other threads:[~2006-06-19 21:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 15:10 [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ Thomas Gleixner
2006-06-18 16:35 ` Michal Piotrowski
2006-06-18 18:28 ` Ingo Molnar
2006-06-19 16:35 ` Michal Piotrowski
2006-06-19 19:51 ` Thomas Gleixner
2006-06-25 13:06 ` Steven Rostedt
2006-06-25 14:26 ` Thomas Gleixner
2006-06-18 19:50 ` Thomas Gleixner
2006-06-19 12:09 ` Con Kolivas
2006-06-19 12:31 ` Thomas Gleixner
2006-06-19 13:05 ` Con Kolivas
2006-06-19 13:10 ` Thomas Gleixner
2006-06-19 21:58 ` mark gross [this message]
2006-06-19 22:19 ` Thomas Gleixner
2006-06-21 12:54 ` Felix Oxley
2006-06-21 13:07 ` Thomas Gleixner
2006-06-18 23:47 ` Roman Zippel
2006-06-19 12:50 ` Ingo Molnar
2006-06-19 13:47 ` Roman Zippel
2006-06-19 5:21 ` Con Kolivas
2006-06-19 5:24 ` Con Kolivas
2006-06-19 12:26 ` Ingo Molnar
2006-06-19 14:03 ` Con Kolivas
2006-06-19 20:06 ` Thomas Gleixner
2006-06-19 20:57 ` ACPI C-States algorithm updates for dyn-tick Dominik Brodowski
2006-06-19 21:28 ` [1/4] ACPI C-States: accounting of sleep states Dominik Brodowski
2006-06-19 21:29 ` [2/4] ACPI C-States: bm_activity improvements Dominik Brodowski
2006-06-19 21:31 ` [3/4] ACPI C-States: only demote on current bus mastering activity Dominik Brodowski
2006-06-19 21:33 ` [4/4 -- only for discussion] ACPI C-States: dyn-ticks-improvements (for -ck implementation) Dominik Brodowski
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=20060619215822.GA4178@linux.intel.com \
--to=mgross@linux.intel.com \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
--cc=tglx@timesys.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 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.