Hi folks,
We are running into a issue on node reboot and on restart of network
manager. Post this activity sometime (NOT always) some of the interfaces do
not come up with configured ip address The configuration on OVS looks like
below
Bridge br_data
Port ecfe_cran
Thank you Ilya & Ben .
Regards
Anju
-Original Message-
From: Ilya Maximets
Sent: Tuesday, January 7, 2020 10:51 PM
To: Ben Pfaff ; Ilya Maximets
Cc: Anju Thomas ; d...@openvswitch.org;
echau...@redhat.com; Rohith Basavaraja ; Keshav
Gupta
Subject: Re: [PATCH v18] Improved Packet
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
Thanks for the review Ilya,
For the below comment
> @@ -7086,10 +7105,16 @@ dp_execute_cb(void *aux_, struct dp_packet_batch
> *packets_,
> * the ownership of these packets. Thus, we can avoid performing
> * the action, because the caller will not use the result
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
Hi Illya,
I am unclear regarding one comment from your end .
You have suggested to put the definition of xlate_error in ifndef __KERNEL__.
But these errors are populated in ofproto layer even otherwise as well.
Regards & Thanks
Anju
-Original Message-
From: Ilya Maximets
Sent:
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
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
Thanks for the review Eelco.
Regards
Anju
-Original Message-
From: Eelco Chaudron
Sent: Tuesday, November 5, 2019 1:23 PM
To: Anju Thomas
Cc: d...@openvswitch.org; i.maxim...@samsung.com; b...@ovn.org; Rohith
Basavaraja ; Keshav Gupta
Subject: Re: [PATCH v14] Improved Packet Drop
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
Hi Eelco,
I have not got any more comments . So I will send out v14 soon. Hopefully there
are no more changes
Regards
Anju
-Original Message-
From: Eelco Chaudron
Sent: Thursday, October 31, 2019 6:08 PM
To: Anju Thomas
Cc: d...@openvswitch.org; i.maxim...@samsung.com; Keshav Gupta
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
Hi Eelco,
Since I have not received any more comments, let me respond to your comments:
-Original Message-
From: Eelco Chaudron
Sent: Tuesday, September 3, 2019 7:27 PM
To: Anju Thomas
Cc: d...@openvswitch.org; Keshav Gupta
Subject: Re: [ovs-dev] [PATCH v12] Improved Packet Drop
13 matches
Mail list logo
