Re: [ovs-discuss] Datapath in OVS-1.10

2013-06-06 Thread Farrukh Aftab Khan
On Jun 6, 2013, at 8:11 AM, Farrukh Aftab Khan < > farrukh.k...@xflowresearch.com> wrote: > > > Hi, > > > > I apologize if my question seems rudimentary but is there a way to add > bridges to different datapaths? From what I understand, in the previous > ver

[ovs-discuss] Datapath in OVS-1.10

2013-06-06 Thread Farrukh Aftab Khan
Hi, I apologize if my question seems rudimentary but is there a way to add bridges to different datapaths? From what I understand, in the previous versions of OVS, datapath and bridges were analogous to each other. Now any new bridge seems to go to the same datapath i.e. ovs-system. Is there a wa

Re: [ovs-discuss] Netperf generates warnings

2012-12-20 Thread Farrukh Aftab Khan
o benchmark OVS-1.7.1 in terms of throughput when the flow table has a million configured flows. Looking forward to seeing the new enhancements. Thank you for the timely reply and all the help. Regards. - Farrukh Aftab Khan xFlow Research Inc. On Thu, Dec 20, 2012 at 12:27 PM, Justin Pettit wro

Re: [ovs-discuss] Netperf generates warnings

2012-12-19 Thread Farrukh Aftab Khan
provided a patch for increasing the buffer space to 1MB to resolve this issue. It is already 1 MB in OVS-1.7.1. So should I increase it further? Is this something to be concerned about? Any heads up would be appreciated. Regards. - Farrukh Aftab Khan On Thu, Dec 20, 2012 at 12:08 PM, Farrukh Aftab Khan

Re: [ovs-discuss] Netperf generates warnings

2012-12-19 Thread Farrukh Aftab Khan
Thanks for the explanation Justin. I have lowered their log levels and I don't these warnings anymore. Thanks for the help. Regards. - Farrukh Aftab Khan xFlow Research Inc. On Wed, Dec 19, 2012 at 10:14 PM, Justin Pettit wrote: > OVS logs these when the CPU usage spikes. That

[ovs-discuss] Netperf generates warnings

2012-12-19 Thread Farrukh Aftab Khan
T00:18:54Z|00058|coverage|INFO|52 events never hit These warnings are only generated when traffic hits the bridge at a high rate. Is it normal for OVS to show these warnings/information messages when dealing with high data rate traffic? Is there a way to hide or minimize them? Regards. - Farrukh

Re: [ovs-discuss] Error writing million flows to OVS bridge

2012-12-13 Thread Farrukh Aftab Khan
Yea sure. Let me first look if memory is indeed an issue with the current version for me, if yes then I'd switch to the newer one available at master. Thanks for the help and suggestion. Regards. - Farrukh Aftab Khan On Fri, Dec 14, 2012 at 12:05 PM, Ben Pfaff wrote: > For what it

Re: [ovs-discuss] Error writing million flows to OVS bridge

2012-12-13 Thread Farrukh Aftab Khan
Memory was the issue. There was only 303 MB of RAM left and hence the crash. Thank you for the help Ben. Much appreciated. - Farrukh Aftab Khan On Fri, Dec 14, 2012 at 11:53 AM, Farrukh Aftab Khan < farrukh.k...@xflowresearch.com> wrote: > Thanks for the quick reply Ben. > >

Re: [ovs-discuss] Error writing million flows to OVS bridge

2012-12-13 Thread Farrukh Aftab Khan
>From what I see from ovs-ofctl dump-tables br0, it should be able to hold maximum of 1 million flows. Am I missing something here? Or have have I overburdened the switch with flows so that it crashes? Regards. - Farrukh Aftab Khan On Fri, Dec 14, 2012 at 11:26 AM, Farrukh Aftab K

Re: [ovs-discuss] Error writing million flows to OVS bridge

2012-12-13 Thread Farrukh Aftab Khan
[Sorry, the last part of the message was somehow truncated] >From what I see here, the table should be able to hold maximum of 1 million flows. Am I missing something here? Or have I overburdened the switch with flows so it crashes? Regards. - Farrukh Aftab Khan On Fri, Dec 14, 2012 at 11

[ovs-discuss] Error writing million flows to OVS bridge

2012-12-13 Thread Farrukh Aftab Khan
Hello, I was trying to push a million flows on br0 using the following loop in a bash script: for((i=0; i<1000; i++)) do src_port=$((65535 - $i)) for((j=0; j<1000; j++)) do dst_port=$((65535 - $j)) ovs-ofctl add-flow br0 priority=65535,idle_t

[ovs-discuss] ovs vxlan vin

2012-11-09 Thread Farrukh Aftab Khan
-- set interface vx1 type=vxlan options:remote_ip=192.168.0.101, options:key=100 They both work fine for me. -Farrukh Aftab Khan >On Oct 26, 2012, at 9:23 AM, JieYue Ma <http://openvswitch.org/mailman/listinfo/discuss>> wrote: >>* I set vlan in another way, e.g. ovs-vsctl add-po