On Wed, Oct 30, 2019 at 09:18:29AM -0700, Gregory Rose wrote: > > On 10/28/2019 9:39 PM, Zhiwei Cen wrote: > >Dear ovs-dev, > > > >I'm trying to see if I can increase the number of flows supported in > >kernel cache. I found two relevant config options > >(other_config:flow-limit and upcall/flow limit). My understanding was > >that other_config:flow-limit is for the normal openflow flows while > >upcall is for the kernel flows > >(http://docs.openvswitch.org/en/latest/faq/design/ question one). > > > >It seems I can change the limit for Openflow flows. > >This works: > >$ovs-vsctl --no-wait set Open_vSwitch . other_config:flow-limit=200001 > > > >$ovs-vsctl --no-wait get Open_vSwitch . other_config:flow-limit > >"200001" > > > >However I cannot change the limit for kernel flows. > >This does not: > >$ovs-appctl upcall/set-flow-limit 200001 > >set flow_limit to 200001 > > > >$ovs-appctl upcall/show > >system@ovs-system: > > flows : (current 70) (avg 68) (max 92) (limit 200000) > > dump duration : 3ms > > ufid enabled : true > > > > 127: (keys 3) > > > >... > > > >My question is, is it possible to change the limit on kernel flows > > I don't know of any way to do that. > I think
$ ovs-vsctl --no-wait set Open_vSwitch . other_config:flow-limit=200001 change the kernel flow limit. William _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
