netdev - Re: [PATCH] Make simple TX hash little endian safe.

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: <20080721151713.GB29543@basil.nowhere.org>
Date:	Mon, 21 Jul 2008 17:17:13 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jarek Poplawski <jarkao2@...il.com>
Cc:	Andi Kleen <andi@...stfloor.org>, davem@...emloft.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH] Make simple TX hash little endian safe.

On Mon, Jul 21, 2008 at 12:32:15PM +0000, Jarek Poplawski wrote:
> On 21-07-2008 10:48, Andi Kleen wrote:
> > From: Andi Kleen <andi@...il.nowhere.org>
> > 
> > Currently it will not use the lower
> > bits at all on big endian system, mapping e.g. all connections to a single
> > queue on a local network which only differs in the low bits.
> 
> It seems ports could be treated similarly, btw?

Ports should be normally better distributed because they tend
to be more uniform than IP addresses due to the way they are
generated, so there will hopefully not be too many endian artifacts. 
But yes at least least folding them too might be a good idea.

-Andi
--
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