diff options
| author | Paolo Abeni <[email protected]> | 2017-05-16 11:20:14 +0200 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2017-05-16 15:41:29 -0400 |
| commit | 2276f58ac5890e58d2b6a48b95493faff7347e3a (patch) | |
| tree | c77ce6fd0b942dfddb145e1ad6dbb2fb1942d849 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 65101aeca52241a05e66f23c96eb896c9412718d (diff) | |
udp: use a separate rx queue for packet reception
under udp flood the sk_receive_queue spinlock is heavily contended.
This patch try to reduce the contention on such lock adding a
second receive queue to the udp sockets; recvmsg() looks first
in such queue and, only if empty, tries to fetch the data from
sk_receive_queue. The latter is spliced into the newly added
queue every time the receive path has to acquire the
sk_receive_queue lock.
The accounting of forward allocated memory is still protected with
the sk_receive_queue lock, so udp_rmem_release() needs to acquire
both locks when the forward deficit is flushed.
On specific scenarios we can end up acquiring and releasing the
sk_receive_queue lock multiple times; that will be covered by
the next patch
Suggested-by: Eric Dumazet <[email protected]>
Signed-off-by: Paolo Abeni <[email protected]>
Acked-by: Eric Dumazet <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions