You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When releasing a DPDK port and asking for detaching/freeing its associated HW resources, care must be taken not to break port "siblings" that were sharing those HW resources.
On device removal, check if the port has siblings
before calling rte_dev_remove.
Fixes: https://github.com/rjarry/grout/issues/40
Signed-off-by: Christophe Fontaine <cfontain@redhat.com>
On device removal, check if the port has siblings
before calling rte_dev_remove.
Fixes: https://github.com/rjarry/grout/issues/40
Signed-off-by: Christophe Fontaine <cfontain@redhat.com>
When releasing a DPDK port and asking for detaching/freeing its associated HW resources, care must be taken not to break port "siblings" that were sharing those HW resources.
See testpmd or OVS:
https://git.dpdk.org/dpdk/tree/app/test-pmd/testpmd.c#n3674
https://github.com/openvswitch/ovs/blob/main/lib/netdev-dpdk.c#L1747
The text was updated successfully, but these errors were encountered: