From: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
To: Andrew Morton <akpm@osdl.org>
Cc: johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1: process start times by procps
Date: Fri, 30 Jan 2004 14:42:36 +0200 [thread overview]
Message-ID: <20040130124236.GA8262@elektroni.ee.tut.fi> (raw)
In-Reply-To: <20040129145148.47cae69a.akpm@osdl.org>
On Thu, Jan 29, 2004 at 02:51:48PM -0800, Andrew Morton wrote:
> Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi> wrote:
> >
> > On Thu, Jan 29, 2004 at 11:48:49AM -0800, john stultz wrote:
> > >
> > > Does George Anzinger's patch work as well?
> >
> > I must have missed that... Any references?
>
> This one.
>
> diff -puN fs/proc/proc_misc.c~proc-stat-btime-fix-2 fs/proc/proc_misc.c
Yes, it works fine: btime stays at the correct value. Just the
ps-output-in-future-problem left.
Linux-2.6.1+patch without ntpd:
passed time according to 'date': 11430.68524 s
timer interrupts: 11432383
interrupts per second: 1000.149
error compared to 1000 interrupts per second: +149 ppm
ps times go towards future about 2.0 s: about 170 ppm
btime stays constant!
clock too fast compared to ntp time by: +0.260461 s
so 'date' is too fast compared to UT by: +22.8 ppm
Linux-2.6.1+patch with ntpd:
passed time according to 'date': 14792.60765 s
timer interrupts: 14795154
interrupts per second: 1000.172
error compared to 1000 interrupts per second: +172 ppm
ps times go towards future about 2.7 s: about 180 ppm
btime stays constant!
(ntp.drift: -21.943)
-Petri
next prev parent reply other threads:[~2004-01-30 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 19:47 Petri Kaukasoina
2004-01-25 11:08 ` Petri Kaukasoina
2004-01-27 15:52 ` Petri Kaukasoina
2004-01-27 17:31 ` Petri Kaukasoina
2004-01-29 2:21 ` john stultz
2004-01-29 14:38 ` Petri Kaukasoina
2004-01-29 19:48 ` john stultz
2004-01-29 20:33 ` Petri Kaukasoina
2004-01-29 22:51 ` Andrew Morton
2004-01-30 12:42 ` Petri Kaukasoina [this message]
2004-01-29 20:13 ` Petri Kaukasoina
2004-02-01 20:18 ` Bill Davidsen
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=20040130124236.GA8262@elektroni.ee.tut.fi \
--to=kaukasoi@elektroni.ee.tut.fi \
--cc=akpm@osdl.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
/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®