Hi, all
When I self-compiled the OVS-2.6 from commit:
commit 7a0f907b2393626dac1387617355990eab69aef7
Author: Justin Pettit
Date: Tue Sep 27 10:13:42 2016 -0700
Set release date for 2.6.0.
Signed-off-by: Justin Pettit
Acked-by: Ben Pfaff
I found that when I using "action=nor
hi, I am a freshman to ovs DPDK, when I tried to launch ovs with dpdk inited, I
found that all the ovs threads are pinned to master lcore,
but I can't find any code for setting the affinity of the specified thread.
Here is my configuration:
lscpu
Architecture: x86_64
CPU op-mode(s):
On 24/10/2016 00:31, "Michael Qiu" <08005...@163.com> wrote:
>Hi, all
>
>
>When I self-compiled the OVS-2.6 from commit:
>
>commit 7a0f907b2393626dac1387617355990eab69aef7
>Author: Justin Pettit
>Date: Tue Sep 27 10:13:42 2016 -0700
>
> Set release date for 2.6.0.
>
> Signed-off-by
On 10/24/2016 11:55 AM, ychen wrote:
> hi, I am a freshman to ovs DPDK, when I tried to launch ovs with dpdk inited,
> I found that all the ovs threads are pinned to master lcore,
> but I can't find any code for setting the affinity of the specified thread.
On older versions of OVS you you can se
Backport commit b59cc14e032da370021794bfd1bdd3d67e88a9a3 from master.
This improves latency compared to current openvswitch 2.5.
Without the patch:
Device 0->1:
Throughput: 6.8683 Mpps
Min. Latency: 39.9780 usec
Avg. Latency: 61.1226 usec
Max. Latency: 89.1110 usec
Device 1->0:
Throug
sorry, I am still confused.
when I launched vswitchd with dpdk-init=false, all the threads changed their
pinned cores as time goes by.
The following output is from ovs version 2.6 with dpdk-init=false
ps -To tid,pid,psr,comm -p 5922
TIDPID PSR COMMAND
5922 5922 12 ovs-vswitchd
5934
在 2016/10/25 1:16, Daniele Di Proietto 写道:
On 24/10/2016 00:31, "Michael Qiu" <08005...@163.com> wrote:
Hi, all
When I self-compiled the OVS-2.6 from commit:
commit 7a0f907b2393626dac1387617355990eab69aef7
Author: Justin Pettit
Date: Tue Sep 27 10:13:42 2016 -0700
Set release
The message was not delivered due to the following reason:
Your message could not be delivered because the destination computer was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely th