Thread (1 message) 1 message, 1 author, 2014-11-14

Re: [PATCH net-next] net: introduce SO_INCOMING_CPU

From: Eric Dumazet <hidden>
Date: 2014-11-14 22:16:11
Also in: linux-api

On Fri, 2014-11-14 at 12:16 -0800, Andy Lutomirski wrote:
Sure, but how do I know that it'll be the same CPU next time?
Because the NIC always use same RX queue for a given flow.

So if you setup your IRQ affinities properly, the same CPU will drain
packets from this RX queue. And since RFS is off, you have the guarantee
the same CPU will be used to process packets in TCP stack.

This SO_INCOMING_CPU info is a hint, there is no guarantee eg if you use
bonding and some load balancer or switch decides to send packets on
different links.

Most NIC use Toeplitz hash, so given the 4-tuple, and rss key (40
bytes), you can actually compute the hash in software and know on which
RX queue traffic should land.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help