[ovs-build] Errored: ovsrobot/ovs#2370 (series_164440 - 69ed627)
builds at travis-ci.org
Sun Mar 15 07:36:59 UTC 2020
Build Update for ovsrobot/ovs
Duration: 38 mins and 51 secs
Commit: 69ed627 (series_164440)
Author: Tonghao Zhang
Message: dpif-netdev: Expand the meter capacity using cmap
For now, ovs-vswitchd use the array of the dp_meter struct
to store meter's data, and at most, there are only 65536
(defined by MAX_METERS) meters that can be used. But in some
case, for example, in the edge gateway, we should use 200,000+,
at least, meters for IP address bandwidth limitation.
Every one IP address will use two meters for its rx and tx
path. In other way, ovs-vswitchd should support meter-offload
(rte_mtr_xxx api introduced by dpdk.), but there are more than
65536 meters in the hardware, such as Mellanox ConnectX-6.
This patch use cmap to manage the meter, instead of the array.
* Insertion performance, ovs-ofctl add-meter 1000+ meters,
the cmap takes abount 4000ms, as same as previous implementation.
* Lookup performance in datapath, we add 1000+ meter which rate is
10G (the NIC cards are 10Gb, so netdev-datapath will not drop the
packets.), and a flow which only forwarding the packets from p0
to p1, with meter action. On other server, the pktgen-dpdk
will generate 64B packets to p0.
The forwarding performance is 4,814,400 pps. Without this path,
4,935,584 pps. There are about 1% performance loss. For addressing
this issue, next patch add a meter cache.
$ in_port=p0,ip,ip_dst=1.1.1.x action=meter:n,output:p1
$ in_port=p1,ip,ip_src=1.1.1.x action=meter:m,output:p0
$ in_port=p0 action=meter:100,output:p1
Cc: Ben Pfaff <blp at ovn.org>
Cc: Jarno Rajahalme <jarno at ovn.org>
Cc: Ilya Maximets <i.maximets at ovn.org>
Cc: Andy Zhou <azhou at ovn.org>
Signed-off-by: Tonghao Zhang <xiangxia.m.yue at gmail.com>
Signed-off-by: 0-day Robot <robot at bytheb.org>
View the changeset: https://github.com/ovsrobot/ovs/commit/69ed627ff165
View the full build log and details: https://travis-ci.org/github/ovsrobot/ovs/builds/662625528?utm_medium=notification&utm_source=email
You can unsubscribe from build emails from the ovsrobot/ovs repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=22285853&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...
More information about the build