[ovs-build] Passed: ovsrobot/ovs#224 (series_86618 - d86300c)
Travis CI
builds at travis-ci.org
Thu Jan 17 05:55:56 UTC 2019
Build Update for ovsrobot/ovs
-------------------------------------
Build: #224
Status: Passed
Duration: 58 mins and 21 secs
Commit: d86300c (series_86618)
Author: Anju Thomas
Message: Improved Packet Drop Statistics in OVS
Currently OVS maintains explicit packet drop/error counters only on port
level. Packets that are dropped as part of normal OpenFlow processing are
counted in flow stats of “drop” flows or as table misses in table stats.
These can only be interpreted by controllers that know the semantics of
the configured OpenFlow pipeline. Without that knowledge, it is impossible
for an OVS user to obtain e.g. the total number of packets dropped due to
OpenFlow rules.
Furthermore, there are numerous other reasons for which packets can be
dropped by OVS slow path that are not related to the OpenFlow pipeline.
The generated datapath flow entries include a drop action to avoid further
expensive upcalls to the slow path, but subsequent packets dropped by the
datapath are not accounted anywhere.
Finally, the datapath itself drops packets in certain error situations.
Also, these drops are today not accounted for.
This makes it difficult for OVS users to monitor packet drop in an OVS
instance and to alert a management system in case of a unexpected increase
of such drops. Also OVS trouble-shooters face difficulties in analysing
packet drops.
With this patch we implement following changes to address the issues
mentioned above.
1. Account and categorize all the packet drops in OVS.
2. Account & classify “drop” action packet drops according to the drop
reason.
3. Identify and account all the silent packet drop scenarios.
4. Display these drops in ovs-appctl coverage/show
5. Modified ovs-appctl dpcls/dump-flows and ovs-appctl dpif/dump-flows
to print drop reason along with drop action
A detailed presentation on this was presented at OvS conference 2017 and
link for the corresponding presentation is available at:
https://www.slideshare.net/LF_OpenvSwitch/lfovs17troubleshooting-the-data-plane-in-ovs-82280329
Sample ovs-appctl dpcls/dump-flows & ovs-appctl dpif/dump-flows displaying drop reason along with drop action.
The idea is to use the coverage infrastructure to maintain the drops
$ ovs-appctl dpctl/dump-flows netdev at ovs-netdev
flow-dump from pmd on cpu core: 0
recirc_id(0),in_port(5),packet_type(ns=0,id=0),eth_type(0x0800),ipv4(frag=no), packets:12, bytes:1176, used:0.884s, actions:drop:recursion too deep
$ ovs-appctl dpif/dump-flows br-int
recirc_id(0),in_port(5),packet_type(ns=0,id=0),eth_type(0x0800),ipv4(frag=no), packets:25, bytes:2450, used:5.008s, actions:drop:recursion too deep
recirc_id(0),in_port(5),packet_type(ns=0,id=0),eth_type(0x0806), packets:7, bytes:294, used:0.009s, actions:drop:recursion too deep
In subsequent commits, we are planning to see if we can use this infrastructure to create a
wrapper to clear and display counters as well.
Co-authored-by: Rohith Basavaraja <rohith.basavaraja at gmail.com>
Co-authored-by: Keshav Gupta <keshugupta1 at gmail.com>
Signed-off-by: Anju Thomas <anju.thomas at ericsson.com>
Signed-off-by: Rohith Basavaraja <rohith.basavaraja at gmail.com>
Signed-off-by: Keshav Gupta <keshugupta1 at gmail.com>
Signed-off-by: 0-day Robot <robot at bytheb.org>
View the changeset: https://github.com/ovsrobot/ovs/commit/d86300c083f0
View the full build log and details: https://travis-ci.org/ovsrobot/ovs/builds/480709890?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...
URL: <http://mail.openvswitch.org/pipermail/ovs-build/attachments/20190117/590099a0/attachment.html>
More information about the build
mailing list