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's worth, O
For what it's worth, OVS from master should use less memory than OVS 1.7
for large numbers of flows, so if that scenario is important then you
should consider using it.
On Fri, Dec 14, 2012 at 12:01:39PM +0500, Farrukh Aftab Khan wrote:
> Memory was the issue. There was only 303 MB of RAM left and
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.
>
> My RAM is 4GB. Th
>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 Khan <
farrukh.
On Fri, Dec 14, 2012 at 11:21:33AM +0500, Farrukh Aftab Khan wrote:
> I am using OVS-1.7.1 on embedded Linux (kernel-2.6.32.27). I am running
> this on OCTEON MIPS processor that has ten cores. After about 0.4 million
> flows, I get the following error and the switch becomes non-responsive. The
> s
[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:21
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
