netdev - Re: [PATCH] bnx2x: add support for receive hashing

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: <4BD62155.7080104@athenacr.com>
Date:	Mon, 26 Apr 2010 19:27:17 -0400
From:	Brian Bloniarz <bmb@...enacr.com>
To:	Rick Jones <rick.jones2@...com>
CC:	David Miller <davem@...emloft.net>, therbert@...gle.com,
	eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH] bnx2x: add support for receive hashing

Rick Jones wrote:
> By and large, customers do not do anything "substantial" with UDP.  NFS
> went to TCP mounts 99 times out of 10 many years ago, leaving DNS as
> about the only thing left*. So, customers will not be chomping at the
> bit for improved UDP scalability/performance.  They would though, be
> jumping up and down demanding iSCSI performance and by implication all
> that comes along for the ride.

I work for a finance firm, and I've met a lot of guys who are
chomping at the bit for improved UDP performance. It's a
huge huge deal in our field. I'm nothing more than one customer
but I have a pretty negative reaction to this sentiment.

I'm also one of the people who occasionally bugs Eric Dumazet
about it :)

One saving grace for the financial multicast case: I think it's
pretty typical for the dest IP to be different for each flow
(different multicast groups). I confirmed on my multi-queue
bnx2 NIC (BCM5709) that those are spread out across the queues,
presumably the hash is similar.
--
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