netdev - RE: ixgbe: 82599 and Westmere with HT

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]

Message-ID: <29F4ED941D916B48B88B4D2A4F3D1B9C01D2F2FE80@orsmsx509.amr.corp.intel.com>
Date:	Thu, 17 Feb 2011 14:06:05 -0800
From:	"Skidmore, Donald C" <donald.c.skidmore@...el.com>
To:	Andrew Dickinson <andrew@...dna.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: ixgbe: 82599 and Westmere with HT


Hey Andrew,

Sorry about the slow reply I'm a bit backed up right now. :)

It sounds like you could be using using RSS hashing?  It's limited to 16 indices.  If you are using Flow Director hashing then maybe your flows aren't varying enough, although from your description it sounds as if they should be.  What if you try something like 'netperf -t TCP_CRR'.

Let me know if any of my assumptions are incorrect.

Thanks,
-Don Skidmore <donald.c.skidmore@...el.com>


>-----Original Message-----
>From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
>On Behalf Of Andrew Dickinson
>Sent: Wednesday, February 16, 2011 5:22 PM
>To: netdev@...r.kernel.org
>Subject: ixgbe: 82599 and Westmere with HT
>
>Hi,
>
>I've got a dual Westmere board (X5675) with an X520 card with dual
>10G.  I see 24-cores exposed to me and the ixgbe driver exposes 24 tx
>and 24 rx interrupts per NIC.  I then pin the interrupts to cores for
>each NIC (each interrupt gets its own core, standard stuff).
>
>Anyway.... I'm only seeing RX interrupts on 16 of the 24 cores (random
>src/dest pairs across a /16 each, so I should be getting good flow
>hashing).  Did I miss some magic somewhere?
>
>I'm running 2.6.32.4, perhaps this has been fixed upstream.  If not,
>any thoughts on how to make this work?
>
>-A
>--
>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
--
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