ip: do not set RFS core on error queue reads
authorSoheil Hassas Yeganeh <soheil@google.com>
Thu, 4 Jan 2018 02:47:10 +0000 (21:47 -0500)
committerDavid S. Miller <davem@davemloft.net>
Fri, 5 Jan 2018 16:14:56 +0000 (11:14 -0500)
We should only record RPS on normal reads and writes.
In single threaded processes, all calls record the same state. In
multi-threaded processes where a separate thread processes
errors, the RFS table mispredicts.

Note that, when CONFIG_RPS is disabled, sock_rps_record_flow
is a noop and no branch is added as a result of this patch.

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>
net/ipv4/af_inet.c

index bab98a4fedadef30fe3e6b38a88bbc98f7b906c9..54cccdd8b1e3f2bfad0b1b81a2478044196703e1 100644 (file)
@@ -790,7 +790,8 @@ int inet_recvmsg(struct socket *sock, struct msghdr *msg, size_t size,
        int addr_len = 0;
        int err;
 
-       sock_rps_record_flow(sk);
+       if (likely(!(flags & MSG_ERRQUEUE)))
+               sock_rps_record_flow(sk);
 
        err = sk->sk_prot->recvmsg(sk, msg, size, flags & MSG_DONTWAIT,
                                   flags & ~MSG_DONTWAIT, &addr_len);