[dpdk-dev] [PATCH v2 4/4] app/testpmd: show example to handle hot unplug

[Iremonger, Bernard]

> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jeff Guo
> Sent: Friday, June 22, 2018 12:51 PM
> To: stephen at networkplumber.org; Richardson, Bruce
> <bruce.richardson at intel.com>; Yigit, Ferruh <ferruh.yigit at intel.com>; Ananyev,
> Konstantin <konstantin.ananyev at intel.com>; gaetan.rivet at 6wind.com; Wu,
> Jingjing <jingjing.wu at intel.com>; thomas at monjalon.net;
> motih at mellanox.com; matan at mellanox.com; Van Haaren, Harry
> <harry.van.haaren at intel.com>; Zhang, Qi Z <qi.z.zhang at intel.com>; He,
> Shaopeng <shaopeng.he at intel.com>
> Cc: jblunck at infradead.org; shreyansh.jain at nxp.com; dev at dpdk.org; Guo, Jia
> <jia.guo at intel.com>; Zhang, Helin <helin.zhang at intel.com>
> Subject: [dpdk-dev] [PATCH v2 4/4] app/testpmd: show example to handle hot
> unplug
> 
> Use testpmd for example, to show how an application smoothly handle failure
> when device being hot unplug. If app have enabled the device event monitor and
> register the hot plug event’s callback before running, once app detect the
> removal event, the callback would be called. It will first stop the packet
> forwarding, then stop the port, close the port, and finally detach the port to
> remove the device out from the device lists.
> 
> Signed-off-by: Jeff Guo <jia.guo at intel.com>
> ---

Acked-by: Bernard Iremonger <bernard.iremonger at intel.com>