Hi Yes. But just consider about how to use DPDK on eth device. During bring up we need: eth_dev_init rte_pktmbuf_pool_create rte_eth_dev_configure rte_eth_rx_queue_setup rte_eth_tx_queue_setup rte_eth_dev_start
All above behavior need to be called by application, pmd driver cannot did all the Recovery without application's help. By the simple notification mechanism, application can simple call following step to recovery: Stop forwarding on this device (rx, tx) rte_eth_dev_close rte_eth_dev_detach rte_eth_dev_attach rte_eth_dev_configure rte_eth_rx_queue_setup rte_eth_tx_queue_setup rte_eth_dev_start Any idea is welcome. We are eager to hear better solution on that. Anyway, no matter whether the recovery is done by application, the patches mentioned Is also useful to notice user about the even. Correct? Thanks Jingjing > -----Original Message----- > From: David Marchand [mailto:david.marchand at 6wind.com] > Sent: Friday, January 22, 2016 4:54 PM > To: Wu, Jingjing > Cc: Zhang, Helin; Ananyev, Konstantin; Lu, Wenzhuo; dev at dpdk.org > Subject: Re: [dpdk-dev] ixgbevf does not recover from pf reset > > Hello, > > On Fri, Jan 22, 2016 at 3:05 AM, Wu, Jingjing <jingjing.wu at intel.com> > wrote: > > Hi, David > > > > We also noticed this issue before. And we are planning to fix this issue. > > And the patch for i40e is ready: > > http://dpdk.org/dev/patchwork/patch/9832/ > > http://dpdk.org/dev/patchwork/patch/9833/ > > > > The solution is that: PF reset interrupt will be captured by DPDK VF, > > then DPDK Call the application's callback function to reset the VF > > device. For i40e device, application need to detach and re-attach the > > device. > > > > For ixgbe, I think the solution would be similar. > > Ok, so to handle a problem in hardware, the application must implement a > new mechanism to recover the port ? > I don't find this solution really elegant ... > > This should be handled by the pmd itself. > > > Regards, > -- > David Marchand
