Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Feb 2002 10:26:13 -0800 (PST)
From:      John Polstra <jdp@polstra.com>
To:        hackers@freebsd.org
Cc:        phk@critter.freebsd.dk
Subject:   Re: A question about timecounters 
Message-ID:  <200202051826.g15IQDt04095@vashon.polstra.com>
In-Reply-To: <90498.1012930272@critter.freebsd.dk>
References:  <90498.1012930272@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <90498.1012930272@critter.freebsd.dk>,
Poul-Henning Kamp  <phk@critter.freebsd.dk> wrote:
> In message <200202051723.g15HNH603801@vashon.polstra.com>, John Polstra writes:
> 
> Can you try to MFC rev 1.111 and see if that changes anything ?

That produced some interesting results.  I am still testing under
very heavy network interrupt load.  With the change from 1.111, I
still get the microuptime messages about as often.  But look how
much larger the reported backwards jumps are:

    microuptime() went backwards (896.225603 -> 888.463636)
    microuptime() went backwards (896.225603 -> 888.494440)
    microuptime() went backwards (896.225603 -> 888.500875)
    microuptime() went backwards (1184.392277 -> 1176.603001)
    microuptime() went backwards (1184.392277 -> 1176.603749)

John
-- 
  John Polstra
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202051826.g15IQDt04095>