I commented on this many weeks/months ago.
Thanks Darrell
On 2/1/18, 2:54 PM, "ovs-discuss-boun...@openvswitch.org on behalf of Ben
Pfaff" wrote:
Darrell, any comment on this? + and ^ are both valid choices of
operator here and it's a little odd that one would be better than the
o
Darrell, any comment on this? + and ^ are both valid choices of
operator here and it's a little odd that one would be better than the
other.
On Thu, Dec 14, 2017 at 08:25:30AM +, liucheng (J) wrote:
>
>
> 发件人: liucheng (J)
> 发送时间: 2017年12月13日 18:01
> 收件人: 'ovs-discuss@openvswitch.org'
> 主题:
Oh, and why are you running multiple instances of OVS? It's unusual.
On Thu, Feb 01, 2018 at 09:22:31AM -0800, Ben Pfaff wrote:
> The rundir for OVS and for ovs-appctl should match. You can do that by
> defining OVS_RUNDIR in the environment for each one, otherwise you end
> up having to give fu
The rundir for OVS and for ovs-appctl should match. You can do that by
defining OVS_RUNDIR in the environment for each one, otherwise you end
up having to give full paths.
On Thu, Feb 01, 2018 at 11:09:42AM -0500, Myra Sh wrote:
> Thank you for your reply.
>
> I tried:
> OVS_RUNDIR=$(pwd)
> exp
Thank you for your reply.
I tried:
OVS_RUNDIR=$(pwd)
exportOVS_RUNDIR
in all nodes.
After that,when I run for example: *"ovs-appctl ofproto/trace br1
in_port=1"* on bridge1, I receive the following message:
*WARN|failed to connect to .../n1.conf/ovs-vswitchd.50.ctl*
there is no ovs-vswitch
Hi Ricardo,
Apologies for the delay. Unfortunately with the OVS 2.9 release I haven’t had
much time to look at this further.
At the very least I think work needs to be done for dpdk.c and netdev-dpdk.c to
enable configuration of VFs specifically (to account for the HW_CRC and VSI
queue configu
