> -----Original Message----- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Jeff Guo > Sent: Friday, June 22, 2018 12:51 PM > To: step...@networkplumber.org; Richardson, Bruce > <bruce.richard...@intel.com>; Yigit, Ferruh <ferruh.yi...@intel.com>; Ananyev, > Konstantin <konstantin.anan...@intel.com>; gaetan.ri...@6wind.com; Wu, > Jingjing <jingjing...@intel.com>; tho...@monjalon.net; > mo...@mellanox.com; ma...@mellanox.com; Van Haaren, Harry > <harry.van.haa...@intel.com>; Zhang, Qi Z <qi.z.zh...@intel.com>; He, > Shaopeng <shaopeng...@intel.com> > Cc: jblu...@infradead.org; shreyansh.j...@nxp.com; dev@dpdk.org; Guo, Jia > <jia....@intel.com>; Zhang, Helin <helin.zh...@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....@intel.com> > ---
Acked-by: Bernard Iremonger <bernard.iremon...@intel.com>
