Re: [PATCH v4] net/kni: reset rte_kni_conf struct before initialization

2022-02-27 Thread Thomas Monjalon
+Cc Ferruh 05/12/2021 07:21, Harold Huang: > When kni driver calls eth_kni_start to start device, some fields such as > min_mtu and max_mtu of rte_kni_conf are not initialized. It will cause > kni_ioctl_create create a kni netdevice with a random min_mtu and max_mtu > value. This isunexpected and

Re: [PATCH v4] net/kni: reset rte_kni_conf struct before initialization

2021-12-22 Thread Harold Huang
The problem this patch wants to solve can be reproduced by ovs-dpdk: 1. create a kni port in ovs: ovs-vsctl add-port ovs-br0 kni0 -- set Interface kni0 type=dpdk options:dpdk-devargs=net_kni0 2. change the mtu of the kni device in kernel: ip link set kni0 mtu 1500 If we do not set rte_kni_conf

[PATCH v4] net/kni: reset rte_kni_conf struct before initialization

2021-12-04 Thread Harold Huang
When kni driver calls eth_kni_start to start device, some fields such as min_mtu and max_mtu of rte_kni_conf are not initialized. It will cause kni_ioctl_create create a kni netdevice with a random min_mtu and max_mtu value. This isunexpected and in some time we could not change the kni device mtu