[RFC,v2,0/2] ethdev: claim device reset as async
mbox series

Message ID 20180910134633.6087-1-qi.z.zhang@intel.com
Headers show
Series
  • ethdev: claim device reset as async
Related show

Message

Zhang, Qi Z Sept. 10, 2018, 1:46 p.m. UTC
Device reset may have the dependency, for example, a VF reset expects
PF ready, or a NIC function as a part of a SOC need to wait for other
parts of the system be ready, these are time-consuming tasks and will
block current thread.

So we claimed rte_eth_dev_reset as an async API, that makes things
easy for an application that what to reset the device from the interrupt
thread since typically a RTE_ETH_EVENT_INTR_RESET handler is invoked
in interrupt thread.

rte_eth_dev_reset will spawn a new thread to call ops->dev_reset, once
it is finished, it will raise the RTE_ETH_EVENT_RESET_COMPLETE event to
notify the application.

Application should not assume device reset is finished after
rte_eth_dev_reset return, it should always wait for a
RTE_ETH_EVENT_RESET_COMPLETE event and check the reset result.

v2:
- rte_eth_dev_reset will spawn a thread.
 
Qi Zhang (2):
  ethdev: claim device reset as async
  testpmd: enable async device reset

 app/test-pmd/testpmd.c         | 50 +++++++++++++++++++++++++++++++++++++++++-
 lib/librte_ethdev/rte_ethdev.c | 48 ++++++++++++++++++++++++++++++++++++++--
 lib/librte_ethdev/rte_ethdev.h | 48 ++++++++++++++++++++++++----------------
 3 files changed, 124 insertions(+), 22 deletions(-)