From: Con Kolivas <kernel@kolivas.org>
To: vatsa@in.ibm.com
Cc: ck@vds.kolivas.org, tony@atomide.com,
tuukka.tikkanen@elektrobit.com, akpm@osdl.org,
johnstul@us.ibm.com, linux-kernel@vger.kernel.org, ak@muc.de,
schwidefsky@de.ibm.com, george@mvista.com
Subject: Re: [ck] [PATCH] dynamic-tick patch modified for SMP
Date: Sun, 14 Aug 2005 10:18:28 +1000 [thread overview]
Message-ID: <200508141018.29668.kernel@kolivas.org> (raw)
In-Reply-To: <20050813164618.GA4659@in.ibm.com>
On Sun, 14 Aug 2005 02:46, Srivatsa Vaddagiri wrote:
> On Sun, Aug 14, 2005 at 12:53:20AM +1000, Con Kolivas wrote:
> > Indeed this fixes it on my P4 so that it does skip ticks. However
> > presumably due to the code change I am having the reverse behaviour from
> > previously - it pauses for ages when using PIT - worse so than previously
> > in that if I dont generate interrupts with my mouse or keyboard it just
> > sits there indefinitely. Having said that, it seems to work fine in APIC
> > mode.
>
> Can you explain what you mean by "pauses for ages when using PIT"? Is it
> while running pmstat? What command line options did you use?
I use vmstat as that is good enough to tell me how many interrupts/s are
occurring. When running 'vmstat 2' for example with PIT mode, vmstat makes
absolutely no progress if I don't move the mouse, even though it's supposed
to update every 2 seconds. Then when I move the mouse it will show something
like 13 tasks running presumably because all of these tasks were waiting on
timers that made no progress until interrupts drove the timers on again. I
built in both PIT and APIC dyntick mode into the kernel and the default in
the way I modified the patch is for APIC mode to be used if it's built in.
After that I modified the values using the sysfs interface at
/sys/devices/system/dyn_tick/dyn_tick0/. In APIC mode it seems to run close to
what it did on the pre-smp version of the dynticks patch but the timers do
seem to be off still with vmstat updating at intervals not consistent with
what parameter is passed to it. It does seems there are some timing issues
with this patch, although it is also quite stable (up for 10 hours now).
I've had a few interesting messages in my syslog suggesting problems:
Hangcheck: hangcheck value past margin!
and then later on a few of:
set_rtc_mmss: can't update from 0 to 59
Cheers,
Con
next prev parent reply other threads:[~2005-08-14 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 20:19 [PATCH] dynamic-tick patch modified for SMP Srivatsa Vaddagiri
2005-08-13 1:35 ` [ck] " Con Kolivas
2005-08-13 6:51 ` Con Kolivas
2005-08-13 11:37 ` Srivatsa Vaddagiri
2005-08-13 14:53 ` Con Kolivas
2005-08-13 16:46 ` Srivatsa Vaddagiri
2005-08-14 0:18 ` Con Kolivas [this message]
2005-08-14 4:15 ` Kyle Moffett
2005-08-15 15:47 ` Srivatsa Vaddagiri
2005-08-15 16:39 ` john stultz
2005-08-16 2:11 ` Srivatsa Vaddagiri
2005-08-15 15:35 ` Srivatsa Vaddagiri
2005-08-15 16:30 ` Con Kolivas
2005-08-16 13:19 ` Srivatsa Vaddagiri
2005-08-16 13:23 ` Con Kolivas
2005-08-17 7:53 ` 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=200508141018.29668.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tony@atomide.com \
--cc=tuukka.tikkanen@elektrobit.com \
--cc=vatsa@in.ibm.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