netdev - Re: [PATCH 1/5] soreuseport: infrastructure

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]

Date:	Wed, 16 Jan 2013 10:37:27 -0800
From:	Tom Herbert <therbert@...gle.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Stephen Hemminger <stephen@...workplumber.org>,
	netdev@...r.kernel.org, davem@...emloft.net,
	netdev@...kandruth.co.uk
Subject: Re: [PATCH 1/5] soreuseport: infrastructure

> Ideally, we should chose a target given by the current CPU number, in
> case SYN messages are spread on all cpus or a set of cpus.
>
It is an ideal, but I don't readily see a practical way to do this
given the available information, the fact that number of sockets
created is up to the application, and the fact that there is no fixed
binding of a socket to CPU.

Consider the simple "cpu % num" algorithm in packet fanout.  Suppose
is a 16 CPU system, and RX queues for the NIC are processed on CPUS
0,3,7,11 and user creates 4 sockets.  In this configuration, on the
first socket would ever be selected!

Tom

> (same idea than PACKET_FANOUT_CPU in net/packet/af_packet.c)
>
>
>
>
--
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