From: Chengwen Feng <fengchengwen@huawei.com>
To: <thomas@monjalon.net>, <ferruh.yigit@xilinx.com>
Cc: <dev@dpdk.org>, <kalesh-anakkur.purayil@broadcom.com>,
<somnath.kotur@broadcom.com>, <ajit.khaparde@broadcom.com>,
<mdr@ashroe.eu>, <Andrew.Rybchenko@oktetlabs.ru>
Subject: [PATCH v8 0/4] ethdev: support error recovery notification
Date: Thu, 16 Jun 2022 17:41:18 +0800 [thread overview]
Message-ID: <20220616094122.1909-1-fengchengwen@huawei.com> (raw)
In-Reply-To: <20220128124830.427-1-kalesh-anakkur.purayil@broadcom.com>
This patchset support error recovery notification.
---
v8: Addressed comments from Thomas and Ferruh.
Also introduced RECOVER_FAIL event.
Add hns3 driver patch.
v7: Addressed comments from Thomas and Andrew.
v6: Addressed comments from Asaf Penso.
1. Updated 20.11 release notes with the new events added.
2. updated testpmd parse_event_printing_config function.
v5: Addressed comments from Ophir Munk.
1. Renamed the new event name to RTE_ETH_EVENT_ERR_RECOVERING.
2. Fixed testpmd logs.
3. Documented the new recovery events.
v4: Addressed comments from Thomas Monjalon
1. Added doxygen comments about new events.
V3: Fixed a typo in commit log.
V2: Added a new event RTE_ETH_EVENT_RESET instead of using the
RTE_ETH_EVENT_INTR_RESET to notify applications about device reset.
Chengwen Feng (1):
net/hns3: support error recovery notification event
Kalesh AP (3):
ethdev: support device error recovery notification
app/testpmd: handle error recovery notification event
net/bnxt: notify applications about device reset/recovery
app/test-pmd/parameters.c | 10 ++++++--
app/test-pmd/testpmd.c | 8 ++++++-
doc/guides/prog_guide/poll_mode_drv.rst | 32 +++++++++++++++++++++++++
doc/guides/rel_notes/release_22_07.rst | 11 +++++++++
drivers/net/bnxt/bnxt_cpr.c | 4 ++++
drivers/net/bnxt/bnxt_ethdev.c | 11 ++++++++-
drivers/net/hns3/hns3_intr.c | 24 +++++++++++++++++++
lib/ethdev/rte_ethdev.h | 6 +++++
8 files changed, 102 insertions(+), 4 deletions(-)
--
2.33.0
next prev parent reply other threads:[~2022-06-16 9:47 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 10:16 [dpdk-dev] [RFC PATCH 0/3] librte_ethdev: error recovery support Kalesh A P
2020-01-22 10:16 ` [dpdk-dev] [RFC PATCH 1/3] librte_ethdev: support device recovery event Kalesh A P
2020-03-11 13:20 ` Thomas Monjalon
2020-03-12 3:31 ` Kalesh Anakkur Purayil
2020-03-12 7:29 ` Thomas Monjalon
2020-01-22 10:16 ` [dpdk-dev] [RFC PATCH 2/3] net/bnxt: notify applications about device reset Kalesh A P
2020-01-22 10:16 ` [dpdk-dev] [RFC PATCH 3/3] app/testpmd: handle device recovery event Kalesh A P
2020-03-11 13:19 ` [dpdk-dev] [RFC PATCH 0/3] librte_ethdev: error recovery support Thomas Monjalon
2020-03-12 3:25 ` Kalesh Anakkur Purayil
2020-03-12 7:34 ` Thomas Monjalon
2020-07-03 16:12 ` Ferruh Yigit
2020-09-30 7:03 ` [dpdk-dev] [RFC V2 " Kalesh A P
2020-09-30 7:03 ` [dpdk-dev] [RFC V2 1/3] ethdev: support device reset and recovery events Kalesh A P
2020-09-30 7:03 ` [dpdk-dev] [RFC V2 2/3] net/bnxt: notify applications about device reset/recovery Kalesh A P
2020-09-30 7:03 ` [dpdk-dev] [RFC V2 3/3] app/testpmd: handle device recovery event Kalesh A P
2020-09-30 7:07 ` [dpdk-dev] [RFC PATCH v2 0/3] librte_ethdev: error recovery support Kalesh A P
2020-09-30 7:07 ` [dpdk-dev] [RFC PATCH v2 1/3] ethdev: support device reset and recovery events Kalesh A P
2020-09-30 7:07 ` [dpdk-dev] [RFC PATCH v2 2/3] net/bnxt: notify applications about device reset/recovery Kalesh A P
2020-09-30 7:07 ` [dpdk-dev] [RFC PATCH v2 3/3] app/testpmd: handle device recovery event Kalesh A P
2020-09-30 7:12 ` [dpdk-dev] [RFC PATCH v3 0/3] librte_ethdev: error recovery support Kalesh A P
2020-09-30 7:12 ` [dpdk-dev] [RFC PATCH v3 1/3] ethdev: support device reset and recovery events Kalesh A P
2020-09-30 7:50 ` Thomas Monjalon
2020-09-30 8:35 ` Kalesh Anakkur Purayil
2020-09-30 9:31 ` Thomas Monjalon
2020-09-30 7:12 ` [dpdk-dev] [RFC PATCH v3 2/3] net/bnxt: notify applications about device reset/recovery Kalesh A P
2020-09-30 7:12 ` [dpdk-dev] [RFC PATCH v3 3/3] app/testpmd: handle device recovery event Kalesh A P
2020-10-08 10:53 ` Asaf Penso
2020-09-30 12:33 ` [dpdk-dev] [RFC PATCH v4 0/3] librte_ethdev: error recovery support Kalesh A P
2020-09-30 12:33 ` [dpdk-dev] [RFC PATCH v4 1/3] ethdev: support device reset and recovery events Kalesh A P
2020-09-30 12:33 ` [dpdk-dev] [RFC PATCH v4 2/3] net/bnxt: notify applications about device reset/recovery Kalesh A P
2020-09-30 12:33 ` [dpdk-dev] [RFC PATCH v4 3/3] app/testpmd: handle device recovery event Kalesh A P
2020-10-06 17:25 ` Ophir Munk
2020-10-07 4:46 ` Kalesh Anakkur Purayil
2020-10-07 8:36 ` Ophir Munk
2020-10-07 9:37 ` Ferruh Yigit
2020-10-07 18:42 ` Ajit Khaparde
2020-10-07 16:49 ` [dpdk-dev] [PATCH v5 0/3] librte_ethdev: error recovery support Kalesh A P
2020-10-07 16:49 ` [dpdk-dev] [PATCH v5 1/3] ethdev: support device reset and recovery events Kalesh A P
2020-10-08 10:49 ` Asaf Penso
2020-10-07 16:49 ` [dpdk-dev] [PATCH v5 2/3] net/bnxt: notify applications about device reset/recovery Kalesh A P
2020-10-07 16:49 ` [dpdk-dev] [PATCH v5 3/3] app/testpmd: handle device recovery event Kalesh A P
2020-10-09 3:48 ` [dpdk-dev] [PATCH v6 0/3] librte_ethdev: error recovery support Kalesh A P
2020-10-09 3:48 ` [dpdk-dev] [PATCH v6 1/3] ethdev: support device reset and recovery events Kalesh A P
2020-10-11 21:29 ` Thomas Monjalon
2020-10-12 8:09 ` Andrew Rybchenko
2021-02-18 15:32 ` Ferruh Yigit
2020-10-09 3:48 ` [dpdk-dev] [PATCH v6 2/3] net/bnxt: notify applications about device reset/recovery Kalesh A P
2020-10-09 3:48 ` [dpdk-dev] [PATCH v6 3/3] app/testpmd: handle device recovery event Kalesh A P
2022-01-28 12:48 ` [dpdk-dev] [PATCH v7 0/4] ethdev: error recovery support Kalesh A P
2022-01-28 12:48 ` [dpdk-dev] [PATCH v7 1/4] ethdev: support device reset and recovery events Kalesh A P
2022-02-01 12:11 ` Ferruh Yigit
2022-02-01 13:09 ` Kalesh Anakkur Purayil
2022-02-01 13:19 ` Ferruh Yigit
2022-02-03 20:28 ` Ajit Khaparde
2022-02-10 22:42 ` Thomas Monjalon
2022-02-01 12:52 ` Ferruh Yigit
2022-02-02 11:44 ` Ray Kinsella
2022-02-10 22:16 ` Thomas Monjalon
2022-02-11 10:09 ` Ray Kinsella
2022-02-14 10:16 ` Ray Kinsella
2022-02-14 11:15 ` Thomas Monjalon
2022-02-14 16:06 ` Ray Kinsella
2022-02-14 16:25 ` Thomas Monjalon
2022-02-14 18:27 ` Ray Kinsella
2022-02-15 13:55 ` Ray Kinsella
2022-02-15 15:12 ` Thomas Monjalon
2022-02-15 16:12 ` Ray Kinsella
2022-05-21 10:33 ` fengchengwen
2022-05-24 15:11 ` Ray Kinsella
2022-06-10 0:16 ` fengchengwen
2022-01-28 12:48 ` [dpdk-dev] [PATCH v7 2/4] app/testpmd: handle device recovery event Kalesh A P
2022-01-28 12:48 ` [dpdk-dev] [PATCH v7 3/4] net/bnxt: notify applications about device reset/recovery Kalesh A P
2022-01-28 12:48 ` [dpdk-dev] [PATCH v7 4/4] doc: update release notes Kalesh A P
2022-02-01 12:12 ` Ferruh Yigit
2022-06-16 9:41 ` Chengwen Feng [this message]
2022-06-16 9:41 ` [PATCH v8 1/4] ethdev: support device error recovery notification Chengwen Feng
2022-06-20 17:42 ` Thomas Monjalon
2022-06-21 1:38 ` fengchengwen
2022-06-21 7:04 ` Thomas Monjalon
2022-09-22 7:53 ` fengchengwen
2022-06-23 15:58 ` Ray Kinsella
2022-06-16 9:41 ` [PATCH v8 2/4] app/testpmd: handle error recovery notification event Chengwen Feng
2022-06-16 9:41 ` [PATCH v8 3/4] net/hns3: support " Chengwen Feng
2022-06-16 9:41 ` [PATCH v8 4/4] net/bnxt: notify applications about device reset/recovery Chengwen Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220616094122.1909-1-fengchengwen@huawei.com \
--to=fengchengwen@huawei.com \
--cc=Andrew.Rybchenko@oktetlabs.ru \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=mdr@ashroe.eu \
--cc=somnath.kotur@broadcom.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).