diff options
author | Soheil Hassas Yeganeh <soheil@google.com> | 2018-01-03 21:47:11 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-01-05 11:14:57 -0500 |
commit | 0a38806f31729c8931383d2ce944115312855931 (patch) | |
tree | 708cc9eada262ba5ae590aecfab1c8db01ea8814 /net/dsa/tag_brcm.c | |
parent | e3f2c4a3db1413bebfd502f7ac94fb55e3ba8c84 (diff) | |
download | linux-0a38806f31729c8931383d2ce944115312855931.tar.gz linux-0a38806f31729c8931383d2ce944115312855931.tar.bz2 linux-0a38806f31729c8931383d2ce944115312855931.zip |
net: revert "Update RFS target at poll for tcp/udp"
On multi-threaded processes, one common architecture is to have
one (or a small number of) threads polling sockets, and a
considerably larger pool of threads reading form and writing to the
sockets. When we set RPS core on tcp_poll() or udp_poll() we essentially
steer all packets of all the polled FDs to one (or small number of)
cores, creaing a bottleneck and/or RPS misprediction.
Another common architecture is to shard FDs among threads pinned
to cores. In such a setting, setting RPS core in tcp_poll() and
udp_poll() is redundant because the RFS core is correctly
set in recvmsg and sendmsg.
Thus, revert the following commit:
c3f1dbaf6e28 ("net: Update RFS target at poll for tcp/udp").
Signed-off-by: Soheil Hassas Yeganeh <soheil@google.com>
Signed-off-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Neal Cardwell <ncardwell@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/dsa/tag_brcm.c')
0 files changed, 0 insertions, 0 deletions