* [dpdk-dev] [RFC v2 0/2] ethdev: claim device reset as async
@ 2018-09-10 13:46 Qi Zhang
0 siblings, 0 replies; 2+ messages in thread
From: Qi Zhang @ 2018-09-10 13:46 UTC (permalink / raw)
To: thomas, konstantin.ananyev, declan.doherty, ferruh.yigit
Cc: dev, benjamin.h.shelton, narender.vangati, beilei.xing,
wenzhuo.lu, Qi Zhang
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(-)
--
2.13.6
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-dev] [RFC v2 0/2] ethdev: claim device reset as async
@ 2018-09-10 13:51 Qi Zhang
0 siblings, 0 replies; 2+ messages in thread
From: Qi Zhang @ 2018-09-10 13:51 UTC (permalink / raw)
To: thomas, konstantin.ananyev, declan.doherty, ferruh.yigit
Cc: dev, benjamin.h.shelton, narender.vangati, Qi Zhang
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(-)
--
2.13.6
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-09-10 13:50 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-10 13:46 [dpdk-dev] [RFC v2 0/2] ethdev: claim device reset as async Qi Zhang
2018-09-10 13:51 Qi Zhang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).