From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/2] ipv6: udp: exploit dev_scratch helpers
Date: Mon, 26 Jun 2017 19:01:49 +0200 [thread overview]
Message-ID: <cover.1498493975.git.pabeni@redhat.com> (raw)
When bringing in the recent cache optimization for the UDP protocol, I forgot
to leverage the newly introduced scratched area helpers in the UDPv6 code path.
As a result, the UDPv6 implementation suffers some unnecessary performance
penality when compared to v4.
This series aim to bring back UDPv6 on equal footing in respect to v4.
The first patch moves the shared helpers to the common include files, while
the second uses them in the UDPv6 code.
This gives 5-8% performance improvement for a system under flood with small
UDPv6 packets. The performance delta is less than the one reported on the
original patch set because the UDPv6 code path already leveraged some of the
optimization.
Paolo Abeni (2):
udp: move scratch area helpers into the include file
ipv6: udp: leverage scratch area helpers
include/net/udp.h | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
net/ipv4/udp.c | 60 ------------------------------------------------------
net/ipv6/udp.c | 14 ++++++++-----
3 files changed, 70 insertions(+), 65 deletions(-)
--
2.9.4
next reply other threads:[~2017-06-26 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 17:01 Paolo Abeni [this message]
2017-06-26 17:01 ` [PATCH net-next 1/2] udp: move scratch area helpers into the include file Paolo Abeni
2017-06-26 17:01 ` [PATCH net-next 2/2] ipv6: udp: leverage scratch area helpers Paolo Abeni
2017-06-27 19:44 ` [PATCH net-next 0/2] ipv6: udp: exploit dev_scratch helpers David Miller
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.1498493975.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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.