From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/2] udp msg_zerocopy
Date: Sat, 24 Nov 2018 14:24:29 -0500 [thread overview]
Message-ID: <20181124192431.32037-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Enable MSG_ZEROCOPY for udp sockets
Patch 1/2 is the main patch, a rebase from RFC patch
http://patchwork.ozlabs.org/patch/899630/
more details in the patch commit message
Patch 2/2 runs the already existing udp zerocopy tests
as part of kselftest
See also recent Linux Plumbers presentation
https://linuxplumbersconf.org/event/2/contributions/106/attachments/104/128/willemdebruijn-lpc2018-udpgso-presentation-20181113.pdf
Willem de Bruijn (2):
udp: msg_zerocopy
tools/testing: extend zerocopy tests to udp
include/linux/skbuff.h | 1 +
net/core/skbuff.c | 15 +++++++++++++-
net/core/sock.c | 5 ++++-
net/ipv4/ip_output.c | 22 ++++++++++++++++++++-
net/ipv6/ip6_output.c | 22 ++++++++++++++++++++-
tools/testing/selftests/net/msg_zerocopy.c | 3 ++-
tools/testing/selftests/net/msg_zerocopy.sh | 2 ++
tools/testing/selftests/net/udpgso_bench.sh | 3 +++
8 files changed, 68 insertions(+), 5 deletions(-)
--
2.20.0.rc0.387.gc7a69e6b6c-goog
next reply other threads:[~2018-11-25 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 19:24 Willem de Bruijn [this message]
2018-11-24 19:24 ` [PATCH net-next 1/2] udp: msg_zerocopy Willem de Bruijn
2018-11-25 1:58 ` David Miller
2018-11-25 2:13 ` Willem de Bruijn
2018-11-24 19:24 ` [PATCH net-next 2/2] tools/testing: extend zerocopy tests to udp Willem de Bruijn
2018-11-25 1:57 ` [PATCH net-next 0/2] udp msg_zerocopy 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=20181124192431.32037-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).