[dpdk-users] How To Handle Hot Remove?

[dpdk-users] How To Handle Hot Remove?

[David Harton (dharton)]

I've looked at the docs online and in the git repo.  I've also looked at what is in test-pmd but I haven't found an answer to the following questions around the scenario where a user pulls out the NIC card of an in-service system.  Or another example would be a user removes an interface from the host KVM config while the guest application is processing packets for that interface.

1) What notification does DPDK provide the application or to gracefully stop the device?
2) Is there any kind of ordering the application has to follow before calling rte_eth_dev_detatch()?

Thanks,
Dave

Re: [dpdk-users] How To Handle Hot Remove?

[Thomas Monjalon]

2016-04-28 23:50, David Harton:
> 1) What notification does DPDK provide the application or to gracefully stop the device?

A rework of hotplug is in progress:
	http://dpdk.org/ml/archives/dev/2016-April/037686.html
Notifications needs to be added.

> 2) Is there any kind of ordering the application has to follow before calling rte_eth_dev_detatch()?

The order is "stop - close - detach":
/**
 * Detach a Ethernet device specified by port identifier.
 * This function must be called when the device is in the
 * closed state.