Re: 24 lost ticks with 2.6.20.10 kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michel Lespinasse wrote:
(I've added the E1000 maintainers to the thread as I found the issue
seems to go away after I compile out that driver. For reference, I was
trying to figure out why I lose exactly 24 ticks about every two
seconds, as shown with report_lost_ticks. This is with a DQ965GF
motherboard with onboard E1000).

that's perfectly likely. The main issue is that we read the hardware stats every two seconds and that can consume quite some time. It's strange that you are losing that many ticks IMHO, but losing one or two might very well be.

We've been playing with all sorts of solutions to this problem and haven't come up with a way to reduce the load of the system reading HW stats, and it remains the most likely culprit, allthough I don't rule out clean routines just yet. This could very well be exaggerated at 100mbit speeds as well, I never looked at that.

I've had good results with 2.6.21.1 (even running tickless :)) on these NICs. Have you tried that yet?

Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux