From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Con Kolivas <kernel@kolivas.org>,
ck@vds.kolivas.org, Tony Lindgren <tony@atomide.com>,
tuukka.tikkanen@elektrobit.com, Andrew Morton <akpm@osdl.org>,
johnstul@us.ibm.com,
linux-kernel Kernel <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@muc.de>,
george@mvista.com
Subject: Re: [ck] [PATCH] dynamic-tick patch modified for SMP
Date: Mon, 15 Aug 2005 21:17:26 +0530 [thread overview]
Message-ID: <20050815154726.GB4731@in.ibm.com> (raw)
In-Reply-To: <6189ECD1-1CE7-4E36-B9F4-FD4D9E5871FA@mac.com>
On Sun, Aug 14, 2005 at 12:15:38AM -0400, Kyle Moffett wrote:
> It may be a good idea to rebase this patch off the new generic time-
> keeping
> subsystem that John Stultz is working on.
I _am_ using the new subsystem interface (->mark_offset) to catch up with lost
ticks. Only I don't think it is that good at catching up the lost ticks if we
skip ticks for few seconds in a stretch. For ex: I am observing drift (time
slows down) when skipping ticks for upto 5 seconds on a 699MHz P3 SMP hardware.
Both TSC and ACPI pm timer give this drift. I am investigating this and will
post an update as soon as I get more information.
--
Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017
next prev parent reply other threads:[~2005-08-15 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 20:19 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
2005-08-14 4:15 ` Kyle Moffett
2005-08-15 15:47 ` Srivatsa Vaddagiri [this message]
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=20050815154726.GB4731@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ck@vds.kolivas.org \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.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
all inboxes | Powered by JetHome®