Show a cover letter.

GET /api/covers/79290/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 79290,
    "url": "http://patchwork.dpdk.org/api/covers/79290/?format=api",
    "web_url": "http://patchwork.dpdk.org/project/dpdk/cover/20200930070326.20133-1-kalesh-anakkur.purayil@broadcom.com/",
    "project": {
        "id": 1,
        "url": "http://patchwork.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": "<20200930070326.20133-1-kalesh-anakkur.purayil@broadcom.com>",
    "list_archive_url": "https://inbox.dpdk.org/dev/20200930070326.20133-1-kalesh-anakkur.purayil@broadcom.com",
    "date": "2020-09-30T07:03:23",
    "name": "[RFC,V2,0/3] librte_ethdev: error recovery support",
    "submitter": {
        "id": 1479,
        "url": "http://patchwork.dpdk.org/api/people/1479/?format=api",
        "name": "Kalesh A P",
        "email": "kalesh-anakkur.purayil@broadcom.com"
    },
    "mbox": "http://patchwork.dpdk.org/project/dpdk/cover/20200930070326.20133-1-kalesh-anakkur.purayil@broadcom.com/mbox/",
    "series": [
        {
            "id": 12609,
            "url": "http://patchwork.dpdk.org/api/series/12609/?format=api",
            "web_url": "http://patchwork.dpdk.org/project/dpdk/list/?series=12609",
            "date": "2020-09-30T07:03:23",
            "name": "librte_ethdev: error recovery support",
            "version": 2,
            "mbox": "http://patchwork.dpdk.org/series/12609/mbox/"
        }
    ],
    "comments": "http://patchwork.dpdk.org/api/covers/79290/comments/",
    "headers": {
        "Return-Path": "<dev-bounces@dpdk.org>",
        "X-Original-To": "patchwork@inbox.dpdk.org",
        "Delivered-To": "patchwork@inbox.dpdk.org",
        "Received": [
            "from dpdk.org (dpdk.org [92.243.14.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id 0D61EA04B1;\n\tWed, 30 Sep 2020 08:50:42 +0200 (CEST)",
            "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 2CFAA1DAF5;\n\tWed, 30 Sep 2020 08:48:54 +0200 (CEST)",
            "from relay.smtp-ext.broadcom.com (lpdvacalvio01.broadcom.com\n [192.19.229.182]) by dpdk.org (Postfix) with ESMTP id 005511DAF1\n for <dev@dpdk.org>; Wed, 30 Sep 2020 08:48:50 +0200 (CEST)",
            "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 038363FE1D;\n Tue, 29 Sep 2020 23:48:48 -0700 (PDT)"
        ],
        "DKIM-Filter": "OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com 038363FE1D",
        "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com;\n s=dkimrelay; t=1601448530;\n bh=kTn64/5UtHqrDRW0QLJoKb7gW72ixO87u5jcBAIswhg=;\n h=From:To:Cc:Subject:Date:In-Reply-To:References:From;\n b=GHa3ddBy3YC5AjbEoNXvVNaThkkpGroG2FlaSuE8sbhI+Pt9bc46M1/m3CuWnuD9n\n w3nzvHcZ3ywOJv/r1GOe9TzcDP7Qm5w0BiVE2tDFbtsptU+Vv2NR7cHxahDFSi/Ws2\n a8v0Uho3yggYOLGLrvg+oIiveol+c5JIzsAmlYHU=",
        "From": "Kalesh A P <kalesh-anakkur.purayil@broadcom.com>",
        "To": "dev@dpdk.org",
        "Cc": "thomas@monjalon.net,\n\tferruh.yigit@intel.com,\n\tajit.khaparde@broadcom.com",
        "Date": "Wed, 30 Sep 2020 12:33:23 +0530",
        "Message-Id": "<20200930070326.20133-1-kalesh-anakkur.purayil@broadcom.com>",
        "X-Mailer": "git-send-email 2.10.1",
        "In-Reply-To": "<20200122101654.20824-1-kalesh-anakkur.purayil@broadcom.com>",
        "References": "<20200122101654.20824-1-kalesh-anakkur.purayil@broadcom.com>",
        "Subject": "[dpdk-dev]  [RFC V2 0/3] librte_ethdev: error recovery support",
        "X-BeenThere": "dev@dpdk.org",
        "X-Mailman-Version": "2.1.15",
        "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",
        "Sender": "\"dev\" <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\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_RESET event to notify\nthe applications about the FW reset or error. In such cases,\nPMD use the RTE_ETH_EVENT_RECOVERED event to notify application about\nPMD has recovered from FW reset or FW error.\n\nV2: Added a new event RTE_ETH_EVENT_RESET instead of using the\nRTE_ETH_EVENT_INTR_RESET to notify applications about device reset.\n\nKalesh AP (3):\n  ethdev: support device reset and recovery events\n  net/bnxt: notify applications about device reset/recovery\n  app/testpmd: handle device recovery event\n\n app/test-pmd/testpmd.c         | 6 +++++-\n drivers/net/bnxt/bnxt_cpr.c    | 3 +++\n drivers/net/bnxt/bnxt_ethdev.c | 9 +++++++++\n lib/librte_ethdev/rte_ethdev.h | 2 ++\n 4 files changed, 19 insertions(+), 1 deletion(-)"
}