From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH net-next 0/2] UDP: introduce RX skb cache
Date: Wed, 18 Apr 2018 12:22:36 +0200 [thread overview]
Message-ID: <cover.1524045911.git.pabeni@redhat.com> (raw)
The goal of this series is to improve UDP performance in the RX path, that
got worse when spectre/meltdown mithigations were introduced.
The main idea is to move almost entirely the cost of skb handling from the
receiver process context into the BH processing, leveraging, for small
packets, a newly introduced, BH managed, skb cache. This is somewhat
similar to copy-break and the implementation details are in the main patch.
Overall this gives a performance improvement up to 20% in for UDP flood
stress test and above 5% for real-life DNS performance tests.
Paolo Abeni (2):
udp: if the rx queue is full, free the skb in
__udp_enqueue_schedule_skb()
udp: implement and use per cpu rx skbs cache
net/ipv4/udp.c | 162 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
net/ipv6/udp.c | 1 -
2 files changed, 160 insertions(+), 3 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-18 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 10:22 Paolo Abeni [this message]
2018-04-18 10:22 ` [PATCH net-next 1/2] udp: if the rx queue is full, free the skb in __udp_enqueue_schedule_skb() Paolo Abeni
2018-04-18 10:22 ` [PATCH net-next 2/2] udp: implement and use per cpu rx skbs cache Paolo Abeni
2018-04-18 16:56 ` Eric Dumazet
2018-04-18 17:15 ` Paolo Abeni
2018-04-18 19:21 ` Eric Dumazet
2018-04-19 7:40 ` Paolo Abeni
2018-04-19 13:47 ` Eric Dumazet
2018-04-20 13:48 ` Jesper Dangaard Brouer
2018-04-21 15:54 ` Willem de Bruijn
2018-04-21 16:45 ` Eric Dumazet
2018-04-22 11:22 ` Paolo Abeni
2018-04-23 8:52 ` Jesper Dangaard Brouer
2018-04-23 8:13 ` Tariq Toukan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1524045911.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.