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, 13 Oct 2009 11:32:43 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Alexander Duyck <alexander.h.duyck@...el.com>
CC:	e1000-list <e1000-devel@...ts.sourceforge.net>,
	Linux Network Development list <netdev@...r.kernel.org>,
	"Allan, Bruce W" <bruce.w.allan@...el.com>,
	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
	"Ronciak, John" <john.ronciak@...el.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	"gospo@...hat.com" <gospo@...hat.com>
Subject: Re: [E1000-devel] behaviour question for igb on nehalem box

On 10/09/2009 05:48 PM, Alexander Duyck wrote:

> The odds of any 2 flows overlapping when you are only using 4 flows is 
> pretty high, especially if the addresses/ports are close in range.  You 
> typically need something on the order of about 16 flows over a wide 
> range of port numbers in order to get a good distribution.

Yes, I realize this.  However, I was surprised that we were seeing the
packet count increasing for only one queue but the interrupt count
increasing for more than one.

Also, if we really crank up the traffic levels the box apparently
panics.  They're working on getting a serial cable hooked up to it to
get the debug information, so I don't really have much information on
that part just yet.

We're going to try the out-of-tree drivers.  Unfortunately it appears
that the out-of-tree igb driver doesn't compile for this kernel.  I
suspect the compat code needs tweaking.

Chris
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ