[ovs-discuss] Limit on num of flows in ovs 2.0

Chetan Bali chetan.bali at aricent.com
Wed Nov 26 09:17:51 UTC 2014

Hi Ben,

I am adding 2000 flows and sending traffic for all the 2000 flows. When 1 packet per flow is send ,I am getting all the 2000 packets at the output interface.

>From the logs,I can see that  2000 flows are getting added at the ovs, but the problem is that ovs is sending add flow request to datapath [ openvswitch.ko ] for only 1251 packets at a time, and only 1250 flows are added at the datapath for burst traffic.

I have taken the output of dump-flow command for ovs and datapath.

Flows count at ovs-ofctl:
ovs-ofctl dump-flows br0 | wc -l

Flows count at datapath [ ovs-dpctl ]:
ovs-dpctl dump-flows | wc -l

It is showing that entries for only 1251 flows is added in datapath table.

1st flow of ovs-ofctl:

cookie=0x0, duration=35.037s, table=0, n_packets=0, n_bytes=0, idle_age=35, ip,in_port=1,dl_src=aa:bb:cc:44:44:44,dl_dst=55:55:55:55:55:55,nw_src=,nw_dst= actions=output:2

we increment dl_src, dl_dst, nw_src, nw_dst by 1 and try to add 2K flows like this.

Chetan Bali

-----Original Message-----
From: Ben Pfaff [mailto:blp at nicira.com]
Sent: 25 November 2014 21:12
To: Chetan Bali
Cc: discuss at openvswitch.org
Subject: Re: [ovs-discuss] Limit on num of flows in ovs 2.0

On Tue, Nov 25, 2014 at 09:41:19AM +0000, Chetan Bali wrote:
> I have a query related to max number of flows added using ovs-ofctl on
> a single ovs bridge. We are trying to find the max limit of ovs flows.
> When we add the flows using ovs-ofctl, we are able to add 2000 flows
> from the ovs clis. But when we send the traffic for 2K flows, only
> ~1250 flows gets added but still we receive the packet outs for 2K
> flows.
> Is there any hard limit on number of flows been added at dpif linux
> class?

There is no hard limit to the OpenFlow flow table.  We routinely run with hundreds of thousands of flows.  I'm confused--you imply that many of the flows you add don't really get added, but that doesn't make any sense.  Can you explain further?
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

More information about the discuss mailing list