From: Tony Lindgren <tony@atomide.com>
To: Peter Gantner <peter.gantner@stud.uni-graz.at>
Cc: linux-kernel@vger.kernel.org, pasi.savolainen@hut.fi,
Charles Lepple <clepple@ghz.cc>,
f.maibaum@web.de
Subject: Re: [PATCH] amd76x_pm on 2.6.0-test9 more cleanup and clock skew test
Date: Mon, 10 Nov 2003 10:04:39 -0800 [thread overview]
Message-ID: <20031110180439.GB1121@atomide.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0311100628440.12413@scourge.crownest.net>
* Peter Gantner <peter.gantner@stud.uni-graz.at> [031109 22:02]:
> Quoting Tony Lindgren from Nov 9
>
> > On the clock skew problem, it's still there, and to figure out how bad the
> > problem is, I've done a little shell script based on the earlier thread on
> > adjtimex on this mailing list.
>
> Here are my results from your script.
Thanks!
> I did three runs each, first run idle, two runs under load, i.e. two
> burnK7 processes and a make -j5 kernel compile just to make sure.
> loadavg goes up to ~6.5 during those.
> ntpd was not running during the tests.
Great, I was only expecting results from idle mode, but seeing what happens
under load is interesting to see too.
> System is an A7M266-d w/ two AthlonXPs 1800+ (model 6 stepping 2),
> L5-modded(!) for the MP setup. (I know this is considered tainting,
> if you can tell me the timing issues are related to the modding I
> will shut up immediately, but so far nobody seems to have pinpointed
> it to this.)
That should not make a difference. I think I'm getting pretty much similar
results with missed ticks. I'll try to take a look at it in early December
when I have access to my Athlon box again.
Tony
prev parent reply other threads:[~2003-11-10 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 0:33 [PATCH] amd76x_pm on 2.6.0-test9 more cleanup and clock skew test Tony Lindgren
2003-11-10 6:01 ` Peter Gantner
2003-11-10 18:04 ` Tony Lindgren [this message]
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=20031110180439.GB1121@atomide.com \
--to=tony@atomide.com \
--cc=clepple@ghz.cc \
--cc=f.maibaum@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pasi.savolainen@hut.fi \
--cc=peter.gantner@stud.uni-graz.at \
/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