[ovs-build] Passed: horms2/ovs#175 (basavapatna/rebalance-v8 - 6e3b7d3)

Travis CI builds at travis-ci.org
Fri Oct 19 08:55:44 UTC 2018


Build Update for horms2/ovs
-------------------------------------

Build: #175
Status: Passed

Duration: 3 mins and 0 secs
Commit: 6e3b7d3 (basavapatna/rebalance-v8)
Author: Sriharsha Basavapatna via dev
Message: revalidator: Rebalance offloaded flows based on the pps rate

This is the third patch in the patch-set to support dynamic rebalancing
of offloaded flows.

The dynamic rebalancing functionality is implemented in this patch. The
ukeys that are not scheduled for deletion are obtained and passed as input
to the rebalancing routine. The rebalancing is done in the context of
revalidation leader thread, after all other revalidator threads are
done with gathering rebalancing data for flows.

For each netdev that is in OOR state, a list of flows - both offloaded
and non-offloaded (pending) - is obtained using the ukeys. For each netdev
that is in OOR state, the flows are grouped and sorted into offloaded and
pending flows.  The offloaded flows are sorted in descending order of
pps-rate, while pending flows are sorted in ascending order of pps-rate.

The rebalancing is done in two phases. In the first phase, we try to
offload all pending flows and if that succeeds, the OOR state on the device
is cleared. If some (or none) of the pending flows could not be offloaded,
then we start replacing an offloaded flow that has a lower pps-rate than
a pending flow, until there are no more pending flows with a higher rate
than an offloaded flow. The flows that are replaced from the device are
added into kernel datapath.

A new OVS configuration parameter "offload-rebalance", is added to ovsdb.
The default value of this is "false". To enable this feature, set the
value of this parameter to "true", which provides packets-per-second
rate based policy to dynamically offload and un-offload flows.

Note: This option can be enabled only when 'hw-offload' policy is enabled.
It also requires 'tc-policy' to be set to 'skip_sw'; otherwise, flow
offload errors (specifically ENOSPC error this feature depends on) reported
by an offloaded device are supressed by TC-Flower kernel module.

Signed-off-by: Sriharsha Basavapatna <sriharsha.basavapatna at broadcom.com>
Co-authored-by: Venkat Duvvuru <venkatkumar.duvvuru at broadcom.com>
Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru at broadcom.com>
Reviewed-by: Sathya Perla <sathya.perla at broadcom.com>
Reviewed-by: Simon Horman <simon.horman at netronome.com>
Reviewed-by: Ben Pfaff <blp at ovn.org>
Signed-off-by: Simon Horman <simon.horman at netronome.com>

View the changeset: https://github.com/horms2/ovs/compare/c178d300c27b...6e3b7d3c1239

View the full build log and details: https://travis-ci.org/horms2/ovs/builds/443360367?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the horms2/ovs repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=20314049&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-build/attachments/20181019/ef75c09c/attachment-0001.html>


More information about the build mailing list