Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Jan 2001 12:58:02 +0100
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        Dag-Erling Smorgrav <des@ofug.org>
Cc:        current@FreeBSD.ORG
Subject:   Re: bogus microuptime() warnings? 
Message-ID:  <15843.979041482@critter>
In-Reply-To: Your message of "09 Jan 2001 12:49:39 %2B0100." <xzp1yudgd2k.fsf@flood.ping.uio.no> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzp1yudgd2k.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes:
>Poul-Henning Kamp <phk@critter.freebsd.dk> writes:
>> No, this is either a problem reading the i8254 timecounter reliably
>> or an interrupt latency problem.
>
>Given that this is -CURRENT, interrupt latency is a likely
>explanation...
>
>Going off on a tangent, I'm getting a lot fewer "hwptr went backwards"
>with the latest -CURRENT than I used to...

That's also the irq-latency if I understand it right.  The latency went
from "abysmal" to "bad" recently.  We used to do "ok".

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


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




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