From: Tom Herbert <therbert@google.com>
To: davem@davemloft.net, tgraf@suug.ch, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] vxlan: Don't use UDP socket for transmit
Date: Sat, 17 Jan 2015 10:18:18 -0800 [thread overview]
Message-ID: <1421518700-22460-1-git-send-email-therbert@google.com> (raw)
UDP socket is not pertinent to transmit for UDP tunnels, checksum
enablement can be done with a socket. This patch set eliminates
reference to a socket in udp_tunnel_xmit functions and in VXLAN
trnasmit.
Also, make GBP, RCO, can CSUM6_RX flags visible to receive socket
and only match these for shareable socket.
Tom Herbert (2):
udp: Do not require sock in udp_tunnel_xmit_skb
vxlan: Eliminate dependency on UDP socket in transmit path
drivers/net/vxlan.c | 66 +++++++++++++++++++++----------------------
include/net/udp_tunnel.h | 16 +++++------
include/net/vxlan.h | 13 +++++----
net/ipv4/udp_tunnel.c | 12 ++++----
net/ipv6/ip6_udp_tunnel.c | 12 ++++----
net/openvswitch/vport-vxlan.c | 6 ++--
6 files changed, 62 insertions(+), 63 deletions(-)
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-01-17 18:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 18:18 Tom Herbert [this message]
2015-01-17 18:18 ` [PATCH net-next 1/2] udp: Do not require sock in udp_tunnel_xmit_skb Tom Herbert
2015-01-17 23:45 ` Jesse Gross
2015-01-18 22:43 ` Or Gerlitz
2015-01-20 17:36 ` Tom Herbert
2015-01-20 21:47 ` Or Gerlitz
2015-01-20 22:24 ` Tom Herbert
2015-01-21 20:57 ` Or Gerlitz
2015-01-21 22:24 ` Tom Herbert
2015-01-21 22:37 ` Or Gerlitz
2015-01-21 22:55 ` Tom Herbert
2015-01-17 18:18 ` [PATCH net-next 2/2] vxlan: Eliminate dependency on UDP socket in transmit path Tom Herbert
2015-01-19 8:59 ` Thomas Graf
2015-01-20 17:29 ` Tom Herbert
2015-01-20 18:13 ` Thomas Graf
2015-01-20 22:53 ` Tom Herbert
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=1421518700-22460-1-git-send-email-therbert@google.com \
--to=therbert@google.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).