linux-kernel - Re: 24 lost ticks with 2.6.20.10 kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 May 2007 15:08:48 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Michel Lespinasse <walken@....org>
CC:	Chuck Ebbert <cebbert@...hat.com>, linux-kernel@...r.kernel.org,
	Dave Jones <davej@...hat.com>, Jeb Cramer <cramerj@...el.com>,
	John Ronciak <john.ronciak@...el.com>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: 24 lost ticks with 2.6.20.10 kernel

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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/