From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Chengwen Feng <fengchengwen@huawei.com>,
thomas@monjalon.net, ferruh.yigit@xilinx.com,
ferruh.yigit@amd.com
Cc: dev@dpdk.org, kalesh-anakkur.purayil@broadcom.com,
somnath.kotur@broadcom.com, ajit.khaparde@broadcom.com,
mdr@ashroe.eu
Subject: Re: [PATCH v13 0/5] support error handling mode
Date: Mon, 17 Oct 2022 10:42:38 +0300 [thread overview]
Message-ID: <f35eb87f-4a0a-18c1-fd66-fe8588e76b85@oktetlabs.ru> (raw)
In-Reply-To: <20221013124227.40123-1-fengchengwen@huawei.com>
On 10/13/22 15:42, Chengwen Feng wrote:
> This patchset introduce error handling mode concept, the supported modes
> are as follows:
>
> 1) PASSIVE: passive error handling, after the PMD detect that a reset
> is required, the PMD reports RTE_ETH_EVENT_INTR_RESET event, and
> application invoke rte_eth_dev_reset to recover the port.
>
> 2) PROACTIVE: proactive error handling, after the PMD detect that a reset
> is required, the PMD reports RTE_ETH_EVENT_ERR_RECOVERING event, and do
> recovery internally, finally, reports the recovery result event.
>
> Chengwen Feng (2):
> ethdev: add error handling mode to device info
> net/hns3: support proactive error handling mode
>
> Kalesh AP (3):
> ethdev: support proactive error handling mode
> app/testpmd: support error handling mode event
> net/bnxt: support proactive error handling mode
>
> ---
> v13: Address comments from Andrew (rework part of rst).
> v12: Address comments from Andrew.
> v11: Fix clang-static fail due wrong experimental placement.
> v10: Accurately describe the recovery success scenario so that
> addressed comments from Ferruh.
> v9: Introduce error handling mode concept.
> Addressed comments from Thomas and Ray.
> 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.
>
> app/test-pmd/config.c | 15 +++++
> app/test-pmd/parameters.c | 10 +++-
> app/test-pmd/testpmd.c | 8 ++-
> doc/guides/prog_guide/poll_mode_drv.rst | 41 +++++++++++++
> doc/guides/rel_notes/release_22_11.rst | 12 ++++
> drivers/net/bnxt/bnxt_cpr.c | 4 ++
> drivers/net/bnxt/bnxt_ethdev.c | 13 ++++-
> drivers/net/e1000/igb_ethdev.c | 2 +
> drivers/net/ena/ena_ethdev.c | 2 +
> drivers/net/hns3/hns3_common.c | 2 +
> drivers/net/hns3/hns3_intr.c | 24 ++++++++
> drivers/net/iavf/iavf_ethdev.c | 2 +
> drivers/net/ixgbe/ixgbe_ethdev.c | 2 +
> drivers/net/txgbe/txgbe_ethdev_vf.c | 2 +
> lib/ethdev/rte_ethdev.h | 77 +++++++++++++++++++++++++
> 15 files changed, 212 insertions(+), 4 deletions(-)
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-10-17 7:42 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220128124831.427-1-kalesh-anakkur.purayil@broadcom.com>
2022-09-22 7:41 ` [PATCH v9 " Chengwen Feng
2022-09-22 7:41 ` [PATCH v9 1/5] ethdev: support get port " Chengwen Feng
2022-10-03 17:35 ` Ferruh Yigit
2022-10-05 1:56 ` fengchengwen
2022-09-22 7:41 ` [PATCH v9 2/5] ethdev: support proactive " Chengwen Feng
2022-10-03 17:35 ` Ferruh Yigit
2022-09-22 7:41 ` [PATCH v9 3/5] app/testpmd: support error handling mode event Chengwen Feng
2022-09-22 7:41 ` [PATCH v9 4/5] net/hns3: support proactive error handling mode Chengwen Feng
2022-09-22 7:41 ` [PATCH v9 5/5] net/bnxt: " Chengwen Feng
2022-10-09 7:53 ` [PATCH v10 0/5] support " Chengwen Feng
2022-10-09 7:53 ` [PATCH v10 1/5] ethdev: support get port " Chengwen Feng
2022-10-09 7:53 ` [PATCH v10 2/5] ethdev: support proactive " Chengwen Feng
2022-10-09 7:53 ` [PATCH v10 3/5] app/testpmd: support error handling mode event Chengwen Feng
2022-10-09 7:53 ` [PATCH v10 4/5] net/hns3: support proactive error handling mode Chengwen Feng
2022-10-09 7:53 ` [PATCH v10 5/5] net/bnxt: " Chengwen Feng
2022-10-09 9:10 ` [PATCH v11 0/5] support " Chengwen Feng
2022-10-09 9:10 ` [PATCH v11 1/5] ethdev: support get port " Chengwen Feng
2022-10-10 8:38 ` Andrew Rybchenko
2022-10-10 8:44 ` Andrew Rybchenko
2022-10-09 9:10 ` [PATCH v11 2/5] ethdev: support proactive " Chengwen Feng
2022-10-10 8:47 ` Andrew Rybchenko
2022-10-11 14:48 ` fengchengwen
2022-10-09 9:10 ` [PATCH v11 3/5] app/testpmd: support error handling mode event Chengwen Feng
2022-10-09 9:10 ` [PATCH v11 4/5] net/hns3: support proactive error handling mode Chengwen Feng
2022-10-09 11:05 ` Dongdong Liu
2022-10-09 9:10 ` [PATCH v11 5/5] net/bnxt: " Chengwen Feng
2022-10-12 3:45 ` [PATCH v12 0/5] support " Chengwen Feng
2022-10-12 3:45 ` [PATCH v12 1/5] ethdev: add error handling mode to device info Chengwen Feng
2022-10-12 3:45 ` [PATCH v12 2/5] ethdev: support proactive error handling mode Chengwen Feng
2022-10-13 8:58 ` Andrew Rybchenko
2022-10-13 12:50 ` fengchengwen
2022-10-12 3:45 ` [PATCH v12 3/5] app/testpmd: support error handling mode event Chengwen Feng
2022-10-12 3:45 ` [PATCH v12 4/5] net/hns3: support proactive error handling mode Chengwen Feng
2022-10-12 3:45 ` [PATCH v12 5/5] net/bnxt: " Chengwen Feng
2022-10-13 12:42 ` [PATCH v13 0/5] support " Chengwen Feng
2022-10-13 12:42 ` [PATCH v13 1/5] ethdev: add error handling mode to device info Chengwen Feng
2022-10-13 12:42 ` [PATCH v13 2/5] ethdev: support proactive error handling mode Chengwen Feng
2022-10-13 12:42 ` [PATCH v13 3/5] app/testpmd: support error handling mode event Chengwen Feng
2022-10-13 12:42 ` [PATCH v13 4/5] net/hns3: support proactive error handling mode Chengwen Feng
2022-10-13 12:42 ` [PATCH v13 5/5] net/bnxt: " Chengwen Feng
2022-10-17 7:42 ` Andrew Rybchenko [this message]
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=f35eb87f-4a0a-18c1-fd66-fe8588e76b85@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--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).