From: Willy Tarreau <w@1wt.eu>
To: Frans Pop <elendil@planet.nl>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"Alexander E. Patrakov" <patrakov@ums.usu.ru>
Subject: Re: Decreasing stime running confuses top (was: top displaying 9999% CPU usage)
Date: Wed, 3 Oct 2007 22:24:46 +0200 [thread overview]
Message-ID: <20071003202446.GQ10199@1wt.eu> (raw)
In-Reply-To: <200710032127.42147.elendil@planet.nl>
On Wed, Oct 03, 2007 at 09:27:41PM +0200, Frans Pop wrote:
> On Wednesday 03 October 2007, you wrote:
> > On Wed, 3 Oct 2007, Ilpo Järvinen wrote:
> > > On Wed, 3 Oct 2007, Frans Pop wrote:
> > > > The only change is in 2 consecutive columns: "2911 502" -> "2912
> > > > 500". Is processor usage calculated from those? Can someone explain
> > > > how?
> > >
> > > The latter seems to be utime ...decreasing. No wonder if arithmetics
> > > will give strange results (probably top is using unsigned delta?)...
> >
> > Hmm, minor miscounting from my side, stime seems more appropriate...
>
> Here is a series showing utime and stime for kontact over 2 minutes.
>
> Values were obtained using (identical values removed):
> $ while true; do awk '{print $14" "$15}' /proc/5269/stat; sleep 1; done | ts
>
> Oct 03 21:17:12 12220 1593
> Oct 03 21:17:18 12221 1594
> Oct 03 21:17:26 12222 1593 <--
> Oct 03 21:17:34 12223 1594
> Oct 03 21:17:43 12224 1594
> Oct 03 21:17:51 12224 1595
> Oct 03 21:17:59 12225 1596
> Oct 03 21:18:07 12226 1595 <--
> Oct 03 21:18:15 12227 1596
> Oct 03 21:18:18 12228 1596
> Oct 03 21:18:22 12229 1595 <--
> Oct 03 21:18:31 12230 1596
> Oct 03 21:18:39 12230 1597
> Oct 03 21:18:44 12231 1597
> Oct 03 21:18:48 12232 1596 <--
> Oct 03 21:18:56 12233 1597
> Oct 03 21:19:04 12234 1596 <--
> Oct 03 21:19:11 12235 1597
>
> So, is it normal that stime decreases sometimes or a kernel bug?
> /me expects the last...
Let me guess... Dual core AMD64 ?
I'm 99.99% sure that if you boot with "notsc", the problem disappears. If
so, you have one of those wonderful AMD64 with unsynced clock and without
HPET to sync with. I wrote a simple program in the past to exhibit the
problem. It would bsimply run "date +%s" in a busy loops and display each
time it would change. Amazing. It could jump back and forth by up to 3
seconds!
Basically, it looked like this :
old=$(date +%s)
while : ; do
x=$(date +%s)
if [ $x != $old ]; then
echo "$old -> $x"
old=$x
fi
done
Regards,
Willy
next prev parent reply other threads:[~2007-10-03 20:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 12:33 top displaying 9999% CPU usage Frans Pop
2007-10-03 12:52 ` Jan Engelhardt
2007-10-03 13:03 ` Alexander E. Patrakov
2007-10-03 14:04 ` Frans Pop
2007-10-03 14:43 ` Ilpo Järvinen
2007-10-03 14:51 ` Ilpo Järvinen
2007-10-03 19:27 ` Decreasing stime running confuses top (was: top displaying 9999% CPU usage) Frans Pop
2007-10-03 20:24 ` Willy Tarreau [this message]
2007-10-03 23:32 ` Frans Pop
2007-10-04 19:19 ` Luca Tettamanti
2007-10-04 19:32 ` Decreasing stime running confuses top Chuck Ebbert
2007-10-04 20:00 ` Christian Borntraeger
2007-10-04 20:21 ` Chuck Ebbert
2007-10-04 21:10 ` [PATCH for testing] " Christian Borntraeger
2007-10-04 22:01 ` Chuck Ebbert
2007-10-04 22:31 ` Christian Borntraeger
2007-10-05 11:43 ` Luca
2007-10-05 15:07 ` Frans Pop
2007-10-05 15:49 ` Frans Pop
2007-10-08 16:49 ` Christian Borntraeger
2007-10-08 17:00 ` Ingo Molnar
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=20071003202446.GQ10199@1wt.eu \
--to=w@1wt.eu \
--cc=elendil@planet.nl \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
/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.