netdev - Re: [PATCH 2/2] packet: Add fanout support.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 05 Jul 2011 20:26:55 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Victor Julien <victor@...iniac.net>
Cc:	"Loke, Chetan" <Chetan.Loke@...scout.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH 2/2] packet: Add fanout support.

Le mardi 05 juillet 2011 à 19:15 +0200, Victor Julien a écrit :
> On 07/05/2011 06:23 PM, Eric Dumazet wrote:
> > Le mardi 05 juillet 2011 à 18:21 +0200, Victor Julien a écrit :
> >> On 07/05/2011 06:16 PM, Eric Dumazet wrote:
> >>> Remember, goal is that _all_ packets of a given flow end in same queue.
> >>>
> >>
> >> What about a hashing scheme based on just the ip addresses? Would make
> >> rxhash useless for this purpose, but would be a lot simpler overall maybe...
> >>
> > 
> > What about loads where a single IP address is used ?
> 
> How would that be a problem?

Say I want my program able to process 2.000.000 packets per second on my
64 cpu machine, but one cpu is only able to process 100.000 pps.

All these packets are coming from IP1, and go to IP2, but thousand of
different flows are in flight.

We need hash function taking into account source port and destination
port.



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