In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes:
>Poul-Henning Kamp <[EMAIL PROTECTED]> 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
[EMAIL PROTECTED] | 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
