On 4/13/24 06:56, Jun Wang wrote:
>>On 4/12/24 08:29, Jun Wang wrote:
>>> If it's a DPDK net_bonding, it may cause
>>> offload-related configurations to take effect,
>>> leading to offload failure.
>>>
>>> /usr/share/openvswitch/scripts/ovs-ctl restart --no-ovs-vswitchd \
>>> --system-id=test
>>>
>On 4/12/24 08:29, Jun Wang wrote:
>> If it's a DPDK net_bonding, it may cause
>> offload-related configurations to take effect,
>> leading to offload failure.
>>
>> /usr/share/openvswitch/scripts/ovs-ctl restart --no-ovs-vswitchd \
>> --system-id=test
>> ovs-vsctl --no-wait set open .
On 4/12/24 08:29, Jun Wang wrote:
> If it's a DPDK net_bonding, it may cause
> offload-related configurations to take effect,
> leading to offload failure.
>
> /usr/share/openvswitch/scripts/ovs-ctl restart --no-ovs-vswitchd \
> --system-id=test
> ovs-vsctl --no-wait set open .
>Hello,
>
>On Fri, Apr 12, 2024 at 8:30 AM Jun Wang wrote:
>>
>> If it's a DPDK net_bonding, it may cause
>> offload-related configurations to take effect,
>> leading to offload failure.
>
>I did not look at the patch for now.
>What is the interest of using a net/bonding DPDK port when there is
Hello,
On Fri, Apr 12, 2024 at 8:30 AM Jun Wang wrote:
>
> If it's a DPDK net_bonding, it may cause
> offload-related configurations to take effect,
> leading to offload failure.
I did not look at the patch for now.
What is the interest of using a net/bonding DPDK port when there is
native
If it's a DPDK net_bonding, it may cause
offload-related configurations to take effect,
leading to offload failure.
/usr/share/openvswitch/scripts/ovs-ctl restart --no-ovs-vswitchd \
--system-id=test
ovs-vsctl --no-wait set open . external-ids:ovn-bridge-datapath-type\
=netdev
ovs-vsctl --no-wait
