diff options
author | David S. Miller <davem@davemloft.net> | 2017-05-16 15:41:31 -0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-05-16 15:41:31 -0400 |
commit | 8dfedc5343401512f80060628263ee0f52937c86 (patch) | |
tree | d69a117f59aeb3a96f42f6b452b471becfa9d803 /net/ipv4/tcp_bbr.c | |
parent | 9dca599b7fa44f01f3635380767da1a5782e4c65 (diff) | |
parent | 6dfb4367cd911d2b03878fffa045d545ba4507f6 (diff) | |
download | linux-8dfedc5343401512f80060628263ee0f52937c86.tar.gz linux-8dfedc5343401512f80060628263ee0f52937c86.tar.bz2 linux-8dfedc5343401512f80060628263ee0f52937c86.zip |
Merge branch 'udp-scalability-improvements'
Paolo Abeni says:
====================
udp: scalability improvements
This patch series implement an idea suggested by Eric Dumazet to
reduce the contention of the udp sk_receive_queue lock when the socket is
under flood.
An ancillary queue is added to the udp socket, and the socket always
tries first to read packets from such queue. If it's empty, we splice
the content from sk_receive_queue into the ancillary queue.
The first patch introduces some helpers to keep the udp code small, and the
following two implement the ancillary queue strategy. The code is split
to hopefully help the reviewing process.
The measured overall gain under udp flood is up to the 30% depending on
the numa layout and the number of ingress queue used by the relevant nic.
The performance numbers have been gathered using pktgen as sender, with 64
bytes packets, random src port on a host b2b connected via a 10Gbs link
with the dut.
The receiver used the udp_sink program by Jesper [1] and an h/w l4 rx hash on
the ingress nic, so that the number of ingress nic rx queues hit by the udp
traffic could be controlled via ethtool -L.
The udp_sink program was bound to the first idle cpu, to get more
stable numbers.
On a single numa node receiver:
nic rx queues vanilla patched kernel
1 1820 kpps 1900 kpps
2 1950 kpps 2500 kpps
16 1670 kpps 2120 kpps
When using a single nic rx queue, busy polling was also enabled,
elsewhere, in the above scenario, the bh processing becomes the bottle-neck
and this produces large artifacts in the measured performances (e.g.
improving the udp sink run time, decreases the overall tput, since more
action from the scheduler comes into play).
[1] https://github.com/netoptimizer/network-testing/blob/master/src/udp_sink.c
v1 -> v2:
Patches 1/3 and 2/3 are unchanged, in patch 3/3 the rx_queue_lock_held param
of udp_rmem_release() is now a bool.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/tcp_bbr.c')
0 files changed, 0 insertions, 0 deletions