On Mon, Feb 13, 2012 at 7:07 PM, Mohit Dhingra wrote:
> Hi All,
>
> I am following the same instructions as given in
> http://openvswitch.org/support/config-cookbooks/qos-rate-limiting/
>
> I have exactly the same setup, except for the measurement host, but I don't
> see any difference in the netp
*Hi All,*
I am following the same instructions as given in
http://openvswitch.org/support/config-cookbooks/qos-rate-limiting/
I have exactly the same setup, except for the measurement host, but I don't
see any difference in the netperf results, I have given more details in the
previous post. Any
On Sun, Feb 12, 2012 at 10:18 AM, Mohit Dhingra wrote:
> Hi Jesse,
>
> Yes, I see your point that there is no benefit of controlling incoming
> traffic, because anyways all traffic will arrive atleast till OVS level from
> physical NIC, so that channel will be the bottleneck anyway.
>
> I configur
On Mon, Feb 13, 2012 at 9:04 AM, Syed Abdullah Shah
<08beeabs...@seecs.edu.pk> wrote:
>
> Hi,
> We are running some tests for which we require multiple OVSs to be deployed
> in the network. I want to clarify some things before we proceed.
> Is there multi-threading employed in the OVS kernel module
Hi,
We are running some tests for which we require multiple OVSs to be deployed
in the network. I want to clarify some things before we proceed.
Is there multi-threading employed in the OVS kernel module? I mean If
we have a cpu containing 16 cores can we run 16 separate ovs kernel
modules so that