Hi, Gurucharan, Many thanks for reply.
I'm sure we did upgrade both user space and kernel module. After upgrade, we did "ovs-ctl force-reload-kmod" to enable the new kernel module. The modinfo output is as follows. $ sudo modinfo openvswitch filename: /lib/modules/3.2.0-49-generic/kernel/net/openvswitch/openvswitch.ko version: 1.11.0 license: GPL description: Open vSwitch switching datapath srcversion: 15A7B31C33618B229A4FAD3 depends: vermagic: 3.2.0-49-generic SMP mod_unload modversions As noted by Sahid, we did observe perform improvement after upgrade. However, we still random saw log drop and fail to flow_del messages. So I'm just wondering whether we've already fully take advantage of megaflow. i.e. Do we need to configure flows in certain ways so as to enable megaflow or make megaflow work better? Many thanks! Jian Qiu On Mon, Oct 21, 2013 at 12:02 AM, Gurucharan Shetty <shet...@nicira.com>wrote: > On Fri, Oct 18, 2013 at 6:05 PM, Jian Qiu <sword...@gmail.com> wrote: > > Hi, > > > > > > Previously, we used ovs 1.4.x and found ovs-vswitchd dropping logs. Then > we > > upgraded to ovs 1.11.0 as suggested on this mailing list. We did observe > > drop of the CPU utilization on host. > > > > However, we still randomly found ovs-vswitchd dropping logs. Some ovs > logs > > are pasted below. > > > > I have two questions: > > > > 1) As megaflow was introduced in ovs 1.11.0, I'm wondering whether > megaflow > > is transparent to userspace? i.e. is there any specific requirement on > flow > > configuration so that we can fully utilize the power of megaflow? > > > > 2) As logs show, we persistently observed "failed to flow_del" messages > in > > our ovs logs. I'm wondering what's the cause for this warning message? > > > > Looking forward to your kind help. > > > > Many thanks. > > > > Jian Qiu > > > > === ovs logs ==== > > > > 2013-10-18T04:00:23Z|4395745|dpif|WARN|Dropped 1120 log messages in last > 1 > > seconds (most recently, 1 seconds ago) due to excessive rate > > 2013-10-18T04:00:23Z|4395746|dpif|WARN|system@ovs-system: failed to > flow_del > > (No such file or directory) > > I think you are not using the kernel module from 1.11 but rather an > old kernel module or the kernel module that comes through linux > kernel. > > > > skb_priority(0),in_port(10),skb_mark(0),eth(src=54:25:8a:6c:5b:9d,dst=00:22:16:3b:ec:0d),eth_type(0x0800),ipv4(src=10.64.13.218,dst=10.64.15.204,proto=6,tos=0,ttl=63,frag=no),tcp(src=4401,dst=49559) > > 2013-10-18T04:00:24Z|4395747|dpif|WARN|Dropped 1120 log messages in last > 1 > > seconds (most recently, 1 seconds ago) due to excessive rate > > 2013-10-18T04:00:24Z|4395748|dpif|WARN|system@ovs-system: failed to > flow_del > > (No such file or directory) > > > skb_priority(0),in_port(10),skb_mark(0),eth(src=54:25:8a:6c:5b:9d,dst=00:22:16:3b:ec:0d),eth_type(0x0800),ipv4(src=10.64.13.218,dst=10.64.15.204,proto=6,tos=0,ttl=63,frag=no),tcp(src=4401,dst=49559) > > 2013-10-18T04:00:25Z|4395749|dpif|WARN|Dropped 1120 log messages in last > 1 > > seconds (most recently, 1 seconds ago) due to excessive rate > > 2013-10-18T04:00:25Z|4395750|dpif|WARN|system@ovs-system: > > f2013-10-18T15:03:18Z|00001|vlog|INFO|opened log file > > /usr/local/var/log/openvswitch/ovs-vswitchd.log > > > > _______________________________________________ > > discuss mailing list > > discuss@openvswitch.org > > http://openvswitch.org/mailman/listinfo/discuss > > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
