From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: john stultz <johnstul@us.ibm.com>, Andi Kleen <ak@suse.de>,
lkml <linux-kernel@vger.kernel.org>,
Tim Schmielau <tim@physik3.uni-rostock.de>,
George Anzinger <george@mvista.com>,
albert@users.sourceforge.net,
Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
Christoph Lameter <clameter@sgi.com>,
Dominik Brodowski <linux@dominikbrodowski.de>,
David Mosberger <davidm@hpl.hp.com>,
Andrew Morton <akpm@osdl.org>,
paulus@samba.org, schwidefsky@de.ibm.com,
keith maanthey <kmannth@us.ibm.com>,
Chris McDermott <lcm@us.ibm.com>, Max Asbock <masbock@us.ibm.com>,
mahuja@us.ibm.com, Darren Hart <darren@dvhart.com>,
"Darrick J. Wong" <djwong@us.ibm.com>,
Anton Blanchard <anton@samba.org>,
donf@us.ibm.com, mpm@selenic.com, benh@kernel.crashing.org
Subject: Re: [PATCH 3/4] new timeofday x86-64 arch specific changes (v. B1)
Date: Thu, 2 Jun 2005 11:39:04 -0700 [thread overview]
Message-ID: <20050602183904.GC2636@us.ibm.com> (raw)
In-Reply-To: <060220051827.15835.429F4FA6000DF9D700003DDB220588617200009A9B9CD3040A029D0A05@comcast.net>
On 02.06.2005 [18:27:51 +0000], Parag Warudkar wrote:
> > If you grab Linus' current tree it should apply.
> >
> > Sorry about the confusion.
> > -john
>
> I ignored the reject since it was from an #include section - the build
> went fine. I am even able to use it successfully. Couple things -
>
> Very happy to report that I no longer get those annoying - "losing
> some ticks ..." "your time source is unreliable or some driver is
> hogging interrupts" messages - Not sure what change in TOD subsystem
> cured it - or was it just the removal of the printk? ;)
>
> Sadly, it somehow feels noticeably slower than vanilla 2.6.12-rc5.
> Especially using X/KDE - It is surely usable but not snappy. I will do
> more research to find out exactly why - but before that is such as
> loss of snappiness possible due to the TOD changes?
Which timesource is being used?
cat /sys/devices/system/timesource/timesource0/timesource
Thanks,
Nish
next prev parent reply other threads:[~2005-06-02 18:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 18:27 [PATCH 3/4] new timeofday x86-64 arch specific changes (v. B1) Parag Warudkar
2005-06-02 18:39 ` Nishanth Aravamudan [this message]
2005-06-02 23:05 ` Parag Warudkar
2005-06-02 23:20 ` john stultz
2005-06-02 23:33 ` Parag Warudkar
2005-06-02 23:50 ` Parag Warudkar
2005-06-03 7:05 ` Ulrich Windl
2005-06-03 15:24 ` john stultz
2005-06-05 17:05 ` Dominik Brodowski
2005-06-06 3:04 ` Parag Warudkar
2005-06-06 3:14 ` Dominik Brodowski
2005-06-10 0:48 ` George Anzinger
2005-06-06 9:21 ` Andi Kleen
2005-06-06 9:24 ` Dominik Brodowski
2005-06-06 9:30 ` Andi Kleen
2005-06-06 13:32 ` Vojtech Pavlik
2005-06-06 22:53 ` john stultz
2005-06-03 16:30 ` Andi Kleen
2005-06-03 18:27 ` john stultz
2005-06-03 19:02 ` Christoph Lameter
2005-06-03 19:21 ` john stultz
2005-06-05 11:27 ` Andi Kleen
2005-06-06 22:51 ` john stultz
2005-06-04 18:40 ` Parag Warudkar
2005-06-05 11:28 ` Andi Kleen
2005-06-05 14:15 ` Parag Warudkar
2005-06-05 20:51 ` Lee Revell
2005-06-05 21:41 ` Parag Warudkar
2005-06-05 22:13 ` Lee Revell
2005-06-06 9:29 ` Andi Kleen
2005-06-06 11:46 ` Parag Warudkar
2005-06-08 13:51 ` Andi Kleen
2005-06-09 1:47 ` Lee Revell
2005-06-09 2:12 ` john stultz
2005-06-09 2:42 ` Parag Warudkar
2005-06-09 14:17 ` Andi Kleen
2005-06-03 13:32 ` Parag Warudkar
2005-06-02 18:40 ` john stultz
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 18:51 Parag Warudkar
2005-06-01 23:09 [PATCH 1/4] new timeofday core subsystem " john stultz
2005-06-01 23:12 ` [PATCH 2/4] new timeofday i386 arch specific changes " john stultz
2005-06-01 23:13 ` [PATCH 3/4] new timeofday x86-64 " john stultz
2005-06-02 0:37 ` Parag Warudkar
2005-06-02 17:34 ` john stultz
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=20050602183904.GC2636@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=albert@users.sourceforge.net \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=clameter@sgi.com \
--cc=darren@dvhart.com \
--cc=davidm@hpl.hp.com \
--cc=djwong@us.ibm.com \
--cc=donf@us.ibm.com \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=kernel-stuff@comcast.net \
--cc=kmannth@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.de \
--cc=mahuja@us.ibm.com \
--cc=masbock@us.ibm.com \
--cc=mpm@selenic.com \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=tim@physik3.uni-rostock.de \
--cc=ulrich.windl@rz.uni-regensburg.de \
/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