[ovs-build] Failed: gvrose8192/ovs-experimental#143 (test-travis - 5557318)
builds at travis-ci.org
Tue Jan 30 17:28:25 UTC 2018
Build Update for gvrose8192/ovs-experimental
Duration: 30 minutes and 19 seconds
Commit: 5557318 (test-travis)
Author: Paolo Abeni
Message: datapath: do not propagate headroom updates to internal port
Author: Paolo Abeni <pabeni at redhat.com>
Date: Thu Nov 30 15:35:33 2017 +0100
openvswitch: do not propagate headroom updates to internal port
After commit 3a927bc7cf9d ("ovs: propagate per dp max headroom to
all vports") the need_headroom for the internal vport is updated
accordingly to the max needed headroom in its datapath.
That avoids the pskb_expand_head() costs when sending/forwarding
packets towards tunnel devices, at least for some scenarios.
We still require such copy when using the ovs-preferred configuration
for vxlan tunnels:
where the route towards the IP 'X' is via 'br_phy'.
When forwarding traffic from the tap towards the vxlan device, we
will call pskb_expand_head() in vxlan_build_skb() because
br-phy->needed_headroom is equal to tun->needed_headroom.
With this change we avoid updating the internal vport needed_headroom,
so that in the above scenario no head copy is needed, giving 5%
performance improvement in UDP throughput test.
As a trade-off, packets sent from the internal port towards a tunnel
device will now experience the head copy overhead. The rationale is
that the latter use-case is less relevant performance-wise.
Signed-off-by: Paolo Abeni <pabeni at redhat.com>
Acked-by: Pravin B Shelar <pshelar at ovn.org>
Signed-off-by: David S. Miller <davem at davemloft.net>
Also removed related compat layer changes.
Cc: Paolo Abeni <pabeni at redhat.com>
Signed-off-by: Greg Rose <gvrose8192 at gmail.com>
View the changeset: https://github.com/gvrose8192/ovs-experimental/compare/test-travis
View the full build log and details: https://travis-ci.org/gvrose8192/ovs-experimental/builds/335245224?utm_source=email&utm_medium=notification
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the build