netdev - Re: flow director and packet ordering

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] [day] [month] [year] [list]

Date:	Mon, 6 Jul 2009 10:55:14 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	David Miller <davem@...emloft.net>
Cc:	peter.p.waskiewicz.jr@...el.com, netdev@...r.kernel.org,
	jeffrey.t.kirsher@...el.com, jesse.brandeburg@...el.com
Subject: Re: flow director and packet ordering

On Sun, Jul 05, 2009 at 06:59:56PM -0700, David Miller wrote:
>
> I personally assume that a master process that accepts connections
> and then hands them off down to worker threads is quite common.

In this scenario I think it might be better to determine which
worker thread to hand the socket to based on the current RX queue
assignment.  This way you won't have to worry about what limit
the hardware has in terms of how many flows it can assign.

Of course if you can't modify the app then you'd have to rely on
hardware assignment.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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