From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH] bnx2x: add support for receive hashing Date: Mon, 26 Apr 2010 11:22:44 -0700 (PDT) Message-ID: <20100426.112244.260086869.davem@davemloft.net> References: <20100426.110432.104061817.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org To: therbert@google.com Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:44976 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754095Ab0DZSWj (ORCPT ); Mon, 26 Apr 2010 14:22:39 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Tom Herbert Date: Mon, 26 Apr 2010 11:19:05 -0700 > This also hits RSS/multiqueue. In a netperf RR test, 500 streams > between my two 16 core AMDs: TCP 970K tps, UDP 370K tps. I'm > surprised they didn't catch that in some benchmarks... Meanwhile, these NIC vendors seem to have all the time in the world to add iSCSI, RDMA and all the other stateful offload junk into their firmware and silicon. Yet they can't hash ports if the protocol is not TCP? Beyond baffling...