From: Paolo Abeni <pabeni@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Pravin Shelar <pshelar@nicira.com>,
Jesse Gross <jesse@kernel.org>, Flavio Leitner <fbl@sysclose.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: [PATCH net-next v3 0/5] bridge/ovs: avoid skb head copy on frame forwarding
Date: Fri, 26 Feb 2016 10:45:36 +0100 [thread overview]
Message-ID: <cover.1456412101.git.pabeni@redhat.com> (raw)
Currently, while when an OVS or Linux bridge is used to forward frames towards
some tunnel device, a skb_head_copy() may occur if the ingress device do not
provide enough headroom for the tx encapsulation.
This patch series tries to address the issue implementing a new ndo operation to
allow the master device to control the headroom used when allocating the skb on
frame reception.
Said operation is used by the Linux bridge to notify the bridged ports of
needed_headroom changes, and similar bookkeeping and behaviour is also added to
openvswitch, on a per datapath basis.
Finally, the operation is implemented for veth and tun device, which give
performance improvement in the 6-12% range when forwarding frames from said
devices towards a vxlan tunnel.
v2:
- fix netdev_get_fwd_headroom() behaviour
- remove some code duplication with the netdev_set_rx_headroom() and
netdev_reset_rx_headroom() helpers
- handle headroom reset on [v]port removal/deletion
- initialize tun align to the old default value
v3:
- fix a comment typo
Paolo Abeni (5):
netdev: introduce ndo_set_rx_headroom
bridge: notify enslaved devices of headroom changes
ovs: propagate per dp max headroom to all vports
net/tun: implement ndo_set_rx_headroom
veth: implement ndo_set_rx_headroom
drivers/net/tun.c | 17 ++++++++++++++-
drivers/net/veth.c | 26 +++++++++++++++++++++++
include/linux/netdevice.h | 31 ++++++++++++++++++++++++++++
net/bridge/br_if.c | 37 +++++++++++++++++++++++++++++++--
net/openvswitch/datapath.c | 40 ++++++++++++++++++++++++++++++++++++
net/openvswitch/datapath.h | 4 ++++
net/openvswitch/vport-internal_dev.c | 10 ++++++++-
7 files changed, 161 insertions(+), 4 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-02-26 9:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 9:45 Paolo Abeni [this message]
2016-02-26 9:45 ` [PATCH net-next v3 1/5] netdev: introduce ndo_set_rx_headroom Paolo Abeni
2016-02-26 9:45 ` [PATCH net-next v3 2/5] bridge: notify enslaved devices of headroom changes Paolo Abeni
2016-02-26 9:45 ` [PATCH net-next v3 3/5] ovs: propagate per dp max headroom to all vports Paolo Abeni
2016-02-26 9:45 ` [PATCH net-next v3 4/5] net/tun: implement ndo_set_rx_headroom Paolo Abeni
2016-02-26 9:45 ` [PATCH net-next v3 5/5] veth: " Paolo Abeni
2016-02-29 19:05 ` [PATCH net-next v3 0/5] bridge/ovs: avoid skb head copy on frame forwarding pravin shelar
2016-03-01 20:54 ` 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.1456412101.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=fbl@sysclose.org \
--cc=hannes@stressinduktion.org \
--cc=jesse@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=stephen@networkplumber.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 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).