netdev - RE: packet received in a wrong rx-queue?

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: <4A6A2125329CFD4D8CC40C9E8ABCAB9F250D8853B7@MILEXCH2.ds.jdsu.net>
Date:	Thu, 19 May 2011 18:48:02 -0700
From:	Jon Zhou <Jon.Zhou@...u.com>
To:	David Miller <davem@...emloft.net>
CC:	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: packet received in a wrong rx-queue?



> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Thursday, May 19, 2011 11:36 AM
> To: Jon Zhou
> Cc: e1000-devel@...ts.sourceforge.net; netdev@...r.kernel.org
> Subject: Re: packet received in a wrong rx-queue?
> 
> From: Jon Zhou <Jon.Zhou@...u.com>
> Date: Wed, 18 May 2011 20:22:07 -0700
> 
> > form the 82599 datasheet, the hash algorithm is consist of src/dst
> > ip, src/dst port,protocol why it got different hash value with same
> > ip/port pair?
> 
> The same reason why feeding different sets of discrete 32-bit and
> 16-bit values to a cryptographic hash results in a different final
> hash value.
> 
> Our software RPS/RFS implementation used to have this quality too.

Even that it gets different hash value, both packets should be delivered to same rx-queue,

Because they are belong to same flow?

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