Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/106660/?format=api
{ "id": 106660, "url": "http://patches.dpdk.org/api/patches/106660/?format=api", "web_url": "http://patches.dpdk.org/project/dpdk/patch/20220128124830.427-1-kalesh-anakkur.purayil@broadcom.com/", "project": { "id": 1, "url": "http://patches.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<20220128124830.427-1-kalesh-anakkur.purayil@broadcom.com>", "list_archive_url": "https://inbox.dpdk.org/dev/20220128124830.427-1-kalesh-anakkur.purayil@broadcom.com", "date": "2022-01-28T12:48:26", "name": "[v7,0/4] ethdev: error recovery support", "commit_ref": null, "pull_url": null, "state": null, "archived": false, "hash": null, "submitter": { "id": 1479, "url": "http://patches.dpdk.org/api/people/1479/?format=api", "name": "Kalesh A P", "email": "kalesh-anakkur.purayil@broadcom.com" }, "delegate": null, "mbox": "http://patches.dpdk.org/project/dpdk/patch/20220128124830.427-1-kalesh-anakkur.purayil@broadcom.com/mbox/", "series": [], "comments": "http://patches.dpdk.org/api/patches/106660/comments/", "check": "pending", "checks": "http://patches.dpdk.org/api/patches/106660/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@inbox.dpdk.org", "Delivered-To": "patchwork@inbox.dpdk.org", "Received": [ "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id B830FA034D;\n\tFri, 28 Jan 2022 13:21:11 +0100 (CET)", "from [217.70.189.124] (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 2743541199;\n\tFri, 28 Jan 2022 13:21:11 +0100 (CET)", "from relay.smtp-ext.broadcom.com (lpdvsmtp10.broadcom.com\n [192.19.11.229]) by mails.dpdk.org (Postfix) with ESMTP id 6036240141\n for <dev@dpdk.org>; Fri, 28 Jan 2022 13:21:09 +0100 (CET)", "from dhcp-10-123-153-22.dhcp.broadcom.net\n (bgccx-dev-host-lnx2.bec.broadcom.net [10.123.153.22])\n by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id 8033FC0000E9;\n Fri, 28 Jan 2022 04:21:07 -0800 (PST)" ], "DKIM-Filter": "OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com 8033FC0000E9", "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com;\n s=dkimrelay; t=1643372468;\n bh=p2TDQi6MS9WWjh4bLoPZvyTntTkKA8yFfDVbLxex6mc=;\n h=From:To:Cc:Subject:Date:In-Reply-To:References:From;\n b=eWBcZ4pEH7dB1YP5wfTVA8ColtlJu0/OvpxUE9+O2xGLdgh4Wduo6e3JPuA61F508\n 0HMeoWd0Gnl4C43nxDOi6le0sXapMCwoxjG6sJ0mqllKfOQWaN3GnqfVnOto4hlL9/\n sumvIDZwoepORKNXd4eQKtL5xKllSmf5VtkCXFZk=", "From": "Kalesh A P <kalesh-anakkur.purayil@broadcom.com>", "To": "dev@dpdk.org", "Cc": "ferruh.yigit@intel.com,\n\tajit.khaparde@broadcom.com,\n\tasafp@nvidia.com", "Subject": "[dpdk-dev] [PATCH v7 0/4] ethdev: error recovery support", "Date": "Fri, 28 Jan 2022 18:18:26 +0530", "Message-Id": "<20220128124830.427-1-kalesh-anakkur.purayil@broadcom.com>", "X-Mailer": "git-send-email 2.10.1", "In-Reply-To": "<20201009034832.10302-1-kalesh-anakkur.purayil@broadcom.com>", "References": "<20201009034832.10302-1-kalesh-anakkur.purayil@broadcom.com>", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.29", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org" }, "content": "From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>\n\nThe error recovery solution is a protocol implemented between firmware\nand bnxt PMD to recover from the fatal errors without a system reboot.\nThere is an alarm thread which constantly monitors the health of the\nfirmware and initiates a recovery when needed.\n\nThere are two scenarios here:\n\n1. Hardware or firmware encountered an error which firmware detected.\n Firmware is in operational status here. In this case, firmware can\n reset the chip and notify the driver about the reset.\n2. Hardware or firmware encountered an error but firmware is dead/hung.\n Firmware is not in operational status. In this case, the only possible\n way to recover the adapter is through host driver(bnxt PMD).\n\nIn both cases, bnxt PMD reinitializes with the FW again after the reset.\nDuring that recovery process, data path will be halted and any control path\noperation would fail. So, the PMD has to notify the application about this\nreset/error event to prevent any activities from the application while\nthe PMD is recovering from the error.\n\nWhile most of the recovery process is transparent to the application since\nmost of the driver ensures recovery from FW reset or FW error conditions,\nthe application will have to reprogram any flows which were offloaded to\nthe underlying hardware.\n\nThis patch set adds support for the reset and recovery event in\nthe rte_eth_event framework. FW error and FW reset conditions would be\nmanaged by the PMD. Driver uses RTE_ETH_EVENT_ERR_RECOVERING event to\nnotify the applications about the FW reset or error.\nPMD uses the RTE_ETH_EVENT_RECOVERED event to notify application about\nPMD has recovered from FW reset or FW error.\nThe application should stop polling till it receives the\nRTE_ETH_EVENT_RECOVERED event from the PMD.\n\nv7: Addressed comments from Thomas and Andrew.\nv6: Addressed comments from Asaf Penso.\n 1. Updated 20.11 release notes with the new events added.\n 2. updated testpmd parse_event_printing_config function.\nv5: Addressed comments from Ophir Munk.\n 1. Renamed the new event name to RTE_ETH_EVENT_ERR_RECOVERING.\n 2. Fixed testpmd logs.\n 3. Documented the new recovery events.\nv4: Addressed comments from Thomas Monjalon\n 1. Added doxygen comments about new events.\nV3: Fixed a typo in commit log.\nV2: Added a new event RTE_ETH_EVENT_RESET instead of using the\n RTE_ETH_EVENT_INTR_RESET to notify applications about device reset.\n\nKalesh AP (4):\n ethdev: support device reset and recovery events\n app/testpmd: handle device recovery event\n net/bnxt: notify applications about device reset/recovery\n doc: update release notes\n\n app/test-pmd/parameters.c | 8 ++++++--\n app/test-pmd/testpmd.c | 10 +++++++++-\n doc/guides/prog_guide/poll_mode_drv.rst | 24 ++++++++++++++++++++++++\n doc/guides/rel_notes/release_22_03.rst | 15 +++++++++++++++\n drivers/net/bnxt/bnxt_cpr.c | 4 ++++\n drivers/net/bnxt/bnxt_ethdev.c | 8 +++++++-\n lib/ethdev/rte_ethdev.h | 18 ++++++++++++++++++\n 7 files changed, 83 insertions(+), 4 deletions(-)", "diff": null, "prefixes": [ "v7", "0/4" ] }