List comments

GET /api/patches/73536/comments/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

[
    {
        "id": 115554,
        "web_url": "https://patches.dpdk.org/comment/115554/",
        "msgid": "<AM4PR05MB3265B90AE9045358E1009C6FD2670@AM4PR05MB3265.eurprd05.prod.outlook.com>",
        "date": "2020-07-08T16:05:53",
        "subject": "Re: [dpdk-dev] [PATCH v5 1/2] mbuf: introduce accurate packet\n\tTx\tscheduling",
        "submitter": {
            "id": 1102,
            "url": "https://patches.dpdk.org/api/people/1102/",
            "name": "Slava Ovsiienko",
            "email": "viacheslavo@mellanox.com"
        },
        "content": "> promote Acked-bt from previous patch version to maintain patchwork status accordingly\n\nAcked-by: Olivier Matz <olivier.matz@6wind.com>\n\n> -----Original Message-----\n> From: dev <dev-bounces@dpdk.org> On Behalf Of Viacheslav Ovsiienko\n> Sent: Wednesday, July 8, 2020 18:47\n> To: dev@dpdk.org\n> Cc: Matan Azrad <matan@mellanox.com>; Raslan Darawsheh\n> <rasland@mellanox.com>; olivier.matz@6wind.com;\n> bernard.iremonger@intel.com; thomas@monjalon.com;\n> mb@smartsharesystems.com\n> Subject: [dpdk-dev] [PATCH v5 1/2] mbuf: introduce accurate packet Tx\n> scheduling\n> \n> There is the requirement on some networks for precise traffic timing\n> management. The ability to send (and, generally speaking, receive) the\n> packets at the very precisely specified moment of time provides the\n> opportunity to support the connections with Time Division Multiplexing using\n> the contemporary general purpose NIC without involving an auxiliary\n> hardware. For example, the supporting of O-RAN Fronthaul interface is one\n> of the promising features for potentially usage of the precise time\n> management for the egress packets.\n> \n> The main objective of this RFC is to specify the way how applications can\n> provide the moment of time at what the packet transmission must be started\n> and to describe in preliminary the supporting this feature from\n> mlx5 PMD side.\n> \n> The new dynamic timestamp field is proposed, it provides some timing\n> information, the units and time references (initial phase) are not explicitly\n> defined but are maintained always the same for a given port.\n> Some devices allow to query rte_eth_read_clock() that will return the current\n> device timestamp. The dynamic timestamp flag tells whether the field\n> contains actual timestamp value. For the packets being sent this value can be\n> used by PMD to schedule packet sending.\n> \n> The device clock is opaque entity, the units and frequency are vendor specific\n> and might depend on hardware capabilities and configurations. If might (or\n> not) be synchronized with real time via PTP, might (or not) be synchronous\n> with CPU clock (for example if NIC and CPU share the same clock source\n> there might be no any drift between the NIC and CPU clocks), etc.\n> \n> After PKT_RX_TIMESTAMP flag and fixed timestamp field deprecation and\n> obsoleting, these dynamic flag and field will be used to manage the\n> timestamps on receiving datapath as well. Having the dedicated flags for\n> Rx/Tx timestamps allows applications not to perform explicit flags reset on\n> forwarding and not to promote received timestamps to the transmitting\n> datapath by default. The static PKT_RX_TIMESTAMP is considered as\n> candidate to become the dynamic flag.\n> \n> When PMD sees the \"rte_dynfield_timestamp\" set on the packet being sent it\n> tries to synchronize the time of packet appearing on the wire with the\n> specified packet timestamp. If the specified one is in the past it should be\n> ignored, if one is in the distant future it should be capped with some\n> reasonable value (in range of seconds). These specific cases (\"too late\" and\n> \"distant future\") can be optionally reported via device xstats to assist\n> applications to detect the time-related problems.\n> \n> There is no any packet reordering according timestamps is supposed, neither\n> within packet burst, nor between packets, it is an entirely application\n> responsibility to generate packets and its timestamps in desired order. The\n> timestamps can be put only in the first packet in the burst providing the\n> entire burst scheduling.\n> \n> PMD reports the ability to synchronize packet sending on timestamp with\n> new offload flag:\n> \n> This is palliative and is going to be replaced with new eth_dev API about\n> reporting/managing the supported dynamic flags and its related features.\n> This API would break ABI compatibility and can't be introduced at the\n> moment, so is postponed to 20.11.\n> \n> For testing purposes it is proposed to update testpmd \"txonly\"\n> forwarding mode routine. With this update testpmd application generates\n> the packets and sets the dynamic timestamps according to specified time\n> pattern if it sees the \"rte_dynfield_timestamp\" is registered.\n> \n> The new testpmd command is proposed to configure sending pattern:\n> \n> set tx_times <burst_gap>,<intra_gap>\n> \n> <intra_gap> - the delay between the packets within the burst\n>               specified in the device clock units. The number\n>               of packets in the burst is defined by txburst parameter\n> \n> <burst_gap> - the delay between the bursts in the device clock units\n> \n> As the result the bursts of packet will be transmitted with specific delays\n> between the packets within the burst and specific delay between the bursts.\n> The rte_eth_get_clock is supposed to be engaged to get the current device\n> clock value and provide the reference for the timestamps.\n> \n> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>\n> \n> ---\n>   v1->v4:\n>      - dedicated dynamic Tx timestamp flag instead of shared with Rx\n>   v4->v5:\n>      - elaborated commit message\n>      - more words about device clocks added,\n>      - note about dedicated Rx/Tx timestamp flags added\n> \n> ---\n>  lib/librte_ethdev/rte_ethdev.c |  1 +\n>  lib/librte_ethdev/rte_ethdev.h |  4 ++++  lib/librte_mbuf/rte_mbuf_dyn.h |\n> 31 +++++++++++++++++++++++++++++++\n>  3 files changed, 36 insertions(+)\n> \n> diff --git a/lib/librte_ethdev/rte_ethdev.c b/lib/librte_ethdev/rte_ethdev.c\n> index 8e10a6f..02157d5 100644\n> --- a/lib/librte_ethdev/rte_ethdev.c\n> +++ b/lib/librte_ethdev/rte_ethdev.c\n> @@ -162,6 +162,7 @@ struct rte_eth_xstats_name_off {\n>  \tRTE_TX_OFFLOAD_BIT2STR(UDP_TNL_TSO),\n>  \tRTE_TX_OFFLOAD_BIT2STR(IP_TNL_TSO),\n>  \tRTE_TX_OFFLOAD_BIT2STR(OUTER_UDP_CKSUM),\n> +\tRTE_TX_OFFLOAD_BIT2STR(SEND_ON_TIMESTAMP),\n>  };\n> \n>  #undef RTE_TX_OFFLOAD_BIT2STR\n> diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h\n> index a49242b..6f6454c 100644\n> --- a/lib/librte_ethdev/rte_ethdev.h\n> +++ b/lib/librte_ethdev/rte_ethdev.h\n> @@ -1178,6 +1178,10 @@ struct rte_eth_conf {\n>  /** Device supports outer UDP checksum */  #define\n> DEV_TX_OFFLOAD_OUTER_UDP_CKSUM  0x00100000\n> \n> +/** Device supports send on timestamp */ #define\n> +DEV_TX_OFFLOAD_SEND_ON_TIMESTAMP 0x00200000\n> +\n> +\n>  #define RTE_ETH_DEV_CAPA_RUNTIME_RX_QUEUE_SETUP 0x00000001\n> /**< Device supports Rx queue setup after device started*/  #define\n> RTE_ETH_DEV_CAPA_RUNTIME_TX_QUEUE_SETUP 0x00000002 diff --git\n> a/lib/librte_mbuf/rte_mbuf_dyn.h b/lib/librte_mbuf/rte_mbuf_dyn.h index\n> 96c3631..8407230 100644\n> --- a/lib/librte_mbuf/rte_mbuf_dyn.h\n> +++ b/lib/librte_mbuf/rte_mbuf_dyn.h\n> @@ -250,4 +250,35 @@ int rte_mbuf_dynflag_lookup(const char *name,\n> #define RTE_MBUF_DYNFIELD_METADATA_NAME\n> \"rte_flow_dynfield_metadata\"\n>  #define RTE_MBUF_DYNFLAG_METADATA_NAME\n> \"rte_flow_dynflag_metadata\"\n> \n> +/**\n> + * The timestamp dynamic field provides some timing information, the\n> + * units and time references (initial phase) are not explicitly defined\n> + * but are maintained always the same for a given port. Some devices\n> +allow\n> + * to query rte_eth_read_clock() that will return the current device\n> + * timestamp. The dynamic Tx timestamp flag tells whether the field\n> +contains\n> + * actual timestamp value for the packets being sent, this value can be\n> + * used by PMD to schedule packet sending.\n> + *\n> + * After PKT_RX_TIMESTAMP flag and fixed timestamp field deprecation\n> + * and obsoleting, the dedicated Rx timestamp flag is supposed to be\n> + * introduced and the shared dynamic timestamp field will be used\n> + * to handle the timestamps on receiving datapath as well.\n> + */\n> +#define RTE_MBUF_DYNFIELD_TIMESTAMP_NAME\n> \"rte_dynfield_timestamp\"\n> +\n> +/**\n> + * When PMD sees the RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME flag\n> set on the\n> + * packet being sent it tries to synchronize the time of packet\n> +appearing\n> + * on the wire with the specified packet timestamp. If the specified\n> +one\n> + * is in the past it should be ignored, if one is in the distant future\n> + * it should be capped with some reasonable value (in range of seconds).\n> + *\n> + * There is no any packet reordering according to timestamps is\n> +supposed,\n> + * neither for packet within the burst, nor for the whole bursts, it is\n> + * an entirely application responsibility to generate packets and its\n> + * timestamps in desired order. The timestamps might be put only in\n> + * the first packet in the burst providing the entire burst scheduling.\n> + */\n> +#define RTE_MBUF_DYNFLAG_TX_TIMESTAMP_NAME\n> \"rte_dynflag_tx_timestamp\"\n> +\n>  #endif\n> --\n> 1.8.3.1",
        "headers": {
            "X-MS-Exchange-CrossTenant-mailboxtype": "HOSTED",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "x-ms-office365-filtering-correlation-id": "8d190d5f-d587-47be-dada-08d82358ca66",
            "x-forefront-prvs": "04583CED1A",
            "X-BeenThere": "dev@dpdk.org",
            "x-ms-exchange-antispam-messagedata": "\n /oIbLqMyFVzQRWfcmYIkV2gvAgvz44TubQeahp4BwJ6Lg5EIHuCmo+0Im5aU5GYPvixejP97E5JphwhzrN25lrIR7nOBESkP9FgXiFPKwqPxmCys8aXip1Z0956WmrPFn8zs3QH7A29u+t5Emgr4/72mFz3pk3qILdJEMOUWgXuv47abX8UkDe//oHDm4SgZMypHvCXCFghndpytqK2q6adrsCrGnhnZdaq1m5yGTAVX60pkeN8j60bSzv6gCptoPid5kPNvV02utuNWWmXWsSFqiKqOlj1NQgcQgfMW8b+00M1zhTTGDvKToKam8dEl6yhykBVNdvOsexwC/a8FreO/aA9LJnD0uduWyEHhWWW6TdQJeCQ3ykUQ+NzM+scW2sgysKYdz8dE/jXcj0B/VTLh2hllM4VrMjlT8bbB3OprFsKT6tuORONeOFn17gRtD2BG6ld8kiJbUyOrgssI/L88kXg/olSt0yyIQ82cnjY=",
            "X-MS-Exchange-CrossTenant-originalarrivaltime": "08 Jul 2020 16:05:53.1238 (UTC)",
            "Message-ID": "\n <AM4PR05MB3265B90AE9045358E1009C6FD2670@AM4PR05MB3265.eurprd05.prod.outlook.com>",
            "x-ld-processed": "a652971c-7d2e-4d9b-a6a4-d149256f461b,ExtFwd",
            "x-ms-oob-tlc-oobclassifiers": "OLM:10000;",
            "x-originating-ip": "[95.164.10.10]",
            "Received": [
                "from dpdk.org (dpdk.org [92.243.14.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id 66CB9A0527;\n\tWed,  8 Jul 2020 18:05:57 +0200 (CEST)",
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 59AF21E49D;\n\tWed,  8 Jul 2020 18:05:56 +0200 (CEST)",
                "from EUR05-AM6-obe.outbound.protection.outlook.com\n (mail-am6eur05on2045.outbound.protection.outlook.com [40.107.22.45])\n by dpdk.org (Postfix) with ESMTP id 10E851E496\n for <dev@dpdk.org>; Wed,  8 Jul 2020 18:05:55 +0200 (CEST)",
                "from AM4PR05MB3265.eurprd05.prod.outlook.com (2603:10a6:205:8::26)\n by AM4PR05MB3459.eurprd05.prod.outlook.com (2603:10a6:205:8::19) with\n Microsoft SMTP Server (version=TLS1_2,\n cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.29; Wed, 8 Jul\n 2020 16:05:53 +0000",
                "from AM4PR05MB3265.eurprd05.prod.outlook.com\n ([fe80::194e:dc46:7543:50ed]) by AM4PR05MB3265.eurprd05.prod.outlook.com\n ([fe80::194e:dc46:7543:50ed%2]) with mapi id 15.20.3174.022; Wed, 8 Jul 2020\n 16:05:53 +0000"
            ],
            "X-MS-Exchange-CrossTenant-userprincipalname": "\n 2hXUTh1cx2aNsamTYKB/M2ccHmeZH67xKFhFvR00RHoZrL3Sxwq2xa65ACnQkWLQzUIdlrjgdg4LT7g2Ewe00v7Wh8eLg/FhxFpGxJ2eJ5A=",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "List-Post": "<mailto:dev@dpdk.org>",
            "x-forefront-antispam-report": "CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;\n IPV:NLI; SFV:NSPM; H:AM4PR05MB3265.eurprd05.prod.outlook.com; PTR:; CAT:NONE;\n SFTY:;\n SFS:(4636009)(39860400002)(136003)(366004)(376002)(396003)(346002)(8936002)(83380400001)(110136005)(316002)(53546011)(6506007)(186003)(52536014)(4326008)(33656002)(5660300002)(26005)(2906002)(71200400001)(54906003)(66946007)(86362001)(478600001)(9686003)(64756008)(66476007)(66446008)(7696005)(55016002)(66556008)(76116006);\n DIR:OUT; SFP:1101;",
            "In-Reply-To": "<1594223249-24629-1-git-send-email-viacheslavo@mellanox.com>",
            "X-MS-Exchange-CrossTenant-AuthAs": "Internal",
            "X-MS-Has-Attach": "",
            "MIME-Version": "1.0",
            "References": "<1591771085-24959-1-git-send-email-viacheslavo@mellanox.com>\n <1594223249-24629-1-git-send-email-viacheslavo@mellanox.com>",
            "X-MS-Exchange-CrossTenant-id": "a652971c-7d2e-4d9b-a6a4-d149256f461b",
            "x-ms-traffictypediagnostic": "AM4PR05MB3459:",
            "Content-Type": "text/plain; charset=\"us-ascii\"",
            "X-MS-Exchange-CrossTenant-Network-Message-Id": "\n 8d190d5f-d587-47be-dada-08d82358ca66",
            "X-MS-Exchange-CrossTenant-AuthSource": "AM4PR05MB3265.eurprd05.prod.outlook.com",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "Accept-Language": "en-US",
            "To": "Slava Ovsiienko <viacheslavo@mellanox.com>, \"dev@dpdk.org\" <dev@dpdk.org>",
            "Content-Language": "en-US",
            "x-ms-exchange-senderadcheck": "1",
            "Thread-Topic": "[dpdk-dev] [PATCH v5 1/2] mbuf: introduce accurate packet Tx\n scheduling",
            "x-microsoft-antispam-prvs": "\n <AM4PR05MB345905E110FA440076B092D3D2670@AM4PR05MB3459.eurprd05.prod.outlook.com>",
            "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com;\n s=selector1;\n h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;\n bh=0spsSM+52/WtGZZW3M+oI4+ESjbuoKdzgYbWp4Qsk38=;\n b=TKIKUsrMFoMf5OI4fr0xXLD7RJKxGpTp5YeNLRcqR3M6RLYfAazVmfhwGy1LjGIy/da6pa1nkSxsrQuDTOXlvDLa+yh57pgaNNZKrTp6aQpWTMr1+RuqgGLxOqD0Kyu/Q8NzrCNAuTwu8BpDh5q6i79cNCm2yvUEO3E04QkcQqg=",
            "Thread-Index": "AQHWVT8dwFwzQaT460KpoxUNys741qj92Fbg",
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>",
            "Delivered-To": "patchwork@inbox.dpdk.org",
            "X-Mailman-Version": "2.1.15",
            "ARC-Seal": "i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;\n b=LZlqWAkxMJS2ZEYkhiT00m0/1MnSjf68T3CH88nOeBgD6znSNshty2z7saC/2KyZ0n8FXm/EpUQKYxhRS9rB0e6jCh8rPq95JRSSfLyg1xRBAvqPmKw33rDXegifDS9pq5dFGji9UGdyRjwfa5w1PGKgdHd2pJ+LU6+zPyMEFUz2THAKKyUL0mRxD3GQVzEu9xF0E8BS/j2r8gcVi8kKx0JrdebJ1yp30m6+40PsMGOBmKXQThXxZf48QYdjM1MaRuMWguR0JscbjarTTelL2XCROFkMq4rH4OU4dRw0mD4d9lzzCcb310stN+p6aDm7GLrfQBCbHXyRLKa5pxVrkA==",
            "Subject": "Re: [dpdk-dev] [PATCH v5 1/2] mbuf: introduce accurate packet\n\tTx\tscheduling",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "X-MS-Exchange-Transport-CrossTenantHeadersStamped": "AM4PR05MB3459",
            "X-OriginatorOrg": "Mellanox.com",
            "X-MS-Exchange-CrossTenant-fromentityheader": "Hosted",
            "X-MS-TNEF-Correlator": "",
            "ARC-Authentication-Results": "i=1; mx.microsoft.com 1; spf=pass\n smtp.mailfrom=mellanox.com; dmarc=pass action=none header.from=mellanox.com;\n dkim=pass header.d=mellanox.com; arc=none",
            "Date": "Wed, 8 Jul 2020 16:05:53 +0000",
            "Precedence": "list",
            "From": "Slava Ovsiienko <viacheslavo@mellanox.com>",
            "Content-Transfer-Encoding": "quoted-printable",
            "authentication-results": "mellanox.com; dkim=none (message not signed)\n header.d=none;mellanox.com; dmarc=none action=none header.from=mellanox.com;",
            "x-microsoft-antispam": "BCL:0;",
            "X-Original-To": "patchwork@inbox.dpdk.org",
            "x-ms-exchange-transport-forked": "True",
            "Errors-To": "dev-bounces@dpdk.org",
            "x-ms-office365-filtering-ht": "Tenant",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "CC": "Matan Azrad <matan@mellanox.com>, Raslan Darawsheh <rasland@mellanox.com>,\n \"olivier.matz@6wind.com\" <olivier.matz@6wind.com>,\n \"bernard.iremonger@intel.com\" <bernard.iremonger@intel.com>,\n \"thomas@monjalon.com\" <thomas@monjalon.com>, \"mb@smartsharesystems.com\"\n <mb@smartsharesystems.com>",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "x-microsoft-antispam-message-info": "\n 96wQOYvohXToFZexr2EZ3tEseqyqtrk+i0BqxeQgKJQO1cVY+E1rILDNbnSiO2Li3djyoQ29pi7dsvdMrbVPqMBWN04a5MRPonB+GBtgcMf4yLQezdcqdcvVUakGaI3xR7EZ7mKJniHBygcfWTTTGW1Ged4UE0jIb9v5RozXXBwS0Qi13rsTlLUZiYL3DMonGInCucpSauBrFH1mARc0fD2jQsEiEYs9GvuNeMdHVTTwpTLRyMjQ9gVx8UjZpPot1unx3pMIT0xlFMsFqWUWElK1SUJ5HWFbHW7Q/IZ9+AZh6AzOB4WhJ6//Z4qMZUTxzFwkyQ2nAlJkSpE22UqKCQ==",
            "x-ms-publictraffictype": "Email",
            "ARC-Message-Signature": "i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;\n s=arcselector9901;\n h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;\n bh=0spsSM+52/WtGZZW3M+oI4+ESjbuoKdzgYbWp4Qsk38=;\n b=ftK8Dfk2Cu0rnK43MfBm0VD/JDHOZQldoO7xWjNO/vnEYQ+j5x/sdvEBwxusYv8GzBSoeeTrqz7SRHEPAYTAMqc9PVdFlBM8vSkDU8LIfxqNrhqS6W5ni1xt7MaWpOVA39oG62JDpg0z8X6NxTgGmnC6TK17A/O6vkDEtca6LBatXrEFAttrwknIzNawlcngW2toUi6sJ+xY6KVwsV+LIN9WT1Sm5RimkorVVaAOhcHCTd7cK4sQdaL2nzx4XU9taxrwGK2ZnaFn5XAK5TSgiGwJ5PyyDfzEqLBURWzQUTVnA0eRGGTeHCrSpC18aKPnZdhx1Trc6c8YZHrmyopm9A=="
        }
    },
    {
        "id": 115620,
        "web_url": "https://patches.dpdk.org/comment/115620/",
        "msgid": "<10029338.slByJQ0L2h@thomas>",
        "date": "2020-07-09T12:26:54",
        "subject": "Re: [dpdk-dev] [PATCH v5 1/2] mbuf: introduce accurate packet Tx\n\tscheduling",
        "submitter": {
            "id": 685,
            "url": "https://patches.dpdk.org/api/people/685/",
            "name": "Thomas Monjalon",
            "email": "thomas@monjalon.net"
        },
        "content": "08/07/2020 17:47, Viacheslav Ovsiienko:\n> There is the requirement on some networks for precise traffic timing\n> management. The ability to send (and, generally speaking, receive)\n> the packets at the very precisely specified moment of time provides\n> the opportunity to support the connections with Time Division\n> Multiplexing using the contemporary general purpose NIC without involving\n> an auxiliary hardware. For example, the supporting of O-RAN Fronthaul\n> interface is one of the promising features for potentially usage of the\n> precise time management for the egress packets.\n[...]\n>  lib/librte_ethdev/rte_ethdev.c |  1 +\n>  lib/librte_ethdev/rte_ethdev.h |  4 ++++\n>  lib/librte_mbuf/rte_mbuf_dyn.h | 31 +++++++++++++++++++++++++++++++\n>  3 files changed, 36 insertions(+)\n\nI think this feature should be added in the release notes.",
        "headers": {
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "Return-Path": "<dev-bounces@dpdk.org>",
            "To": "Viacheslav Ovsiienko <viacheslavo@mellanox.com>",
            "X-ME-Proxy-Cause": "\n gggruggvucftvghtrhhoucdtuddrgeduiedrudelgdehfecutefuodetggdotefrodftvf\n curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu\n uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc\n fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs\n ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf\n frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei\n iedvffegheenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih\n iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho\n nhdrnhgvth",
            "DKIM-Signature": [
                "v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=\n from:to:cc:subject:date:message-id:in-reply-to:references\n :mime-version:content-transfer-encoding:content-type; s=fm1; bh=\n 6NnHu8jOiNSFpbmDgBMIiPVJDNLlEYs548P32sFi7fs=; b=jOg3SCKbit20EDnV\n 3Bwt5soga92V+C9Z7AHoL2JOMt8vHAdUhKRP4oEMCL3OiQ6atsaOKrfxPMqYjBrW\n gpi1zWTXXABwQWtQHT5u6LUbNUIEVgFu/3rC3LlO+OCtmauiAGB9qfHwQFvhRTUI\n hOhZjVi8qQ6G0J5HaBLdmLpuH77osKok+n3lA4QnTBW4bXjJ+ywt0INPl7LRXI3+\n gTWlG5giT3aGJF7taTepQJM7Pw1EprMfTfgoAeBHHIgoE80KWh9RLyzJfBAbTRVC\n oRcJIDIATfzKkbYTU3z2/Uc+ejehSVELzA9kCsZGSkjEYoyBxQIVf3pE+lIh9Nu0\n ktzbqg==",
                "v=1; a=rsa-sha256; c=relaxed/relaxed; d=\n messagingengine.com; h=cc:content-transfer-encoding:content-type\n :date:from:in-reply-to:message-id:mime-version:references\n :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender\n :x-sasl-enc; s=fm3; bh=6NnHu8jOiNSFpbmDgBMIiPVJDNLlEYs548P32sFi7\n fs=; b=rqiGIDHcA11u1S4DZ4R19738doYvBuT2E1InJKE0Va1rm1vqekk9V/Tgy\n O4g7t4W6AhNRz6iPDeepmcxeoToO058GrauKdZ5pDghh9jy8EfkFhuJ8MMEzAND0\n dYpPtXXrvyLwAEPIZ1q5sv6YHWA9uO7p0vzfAT7TYSY0LVQAZH5gzr8r62iGllTZ\n W2CGksn8Jzwy//tyFlpAGstcL8rqDVQgY+/j1qQtv81adqtbjTYhXvg/iSBe8fTc\n rn4Y0hlFr8Emo045quKTLiKgNKZQ+tZybE3v8GSI25N2l4/WUwCCz3JbhBzuY4T0\n B0JoHOJMsy05+gLw1IpNMW6RCQZgg=="
            ],
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>",
            "X-ME-Proxy": "<xmx:EQ0HX1ZjkGkdTbymZ5G66qS99oUYb_cKE3kOU78MFqXCYuk1zo0ZYA>\n <xmx:EQ0HX8_nYcqCtX5m2jMZw_dZMAsKl8BVLvLY6EKNOVdmUpUMfrHmbA>\n <xmx:EQ0HX0oZq5tUYub5kjwSgmzKg56fLmYg24wgjSAqtn7IV7_AghE9BA>\n <xmx:EQ0HX0VvjQbJx9MX6TyrcLXWdPB4mkkP8DMUf1KeuLr_NCVtEJ5Yew>",
            "X-ME-Sender": "<xms:EQ0HXyZ_oIAsQteP9FI-cImdeElW_OlVBajoVr_VMmDqCP-xAwQbbQ>",
            "X-BeenThere": "dev@dpdk.org",
            "Received": [
                "from dpdk.org (dpdk.org [92.243.14.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id A3E2EA0528;\n\tThu,  9 Jul 2020 14:26:59 +0200 (CEST)",
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 78ED21E87B;\n\tThu,  9 Jul 2020 14:26:59 +0200 (CEST)",
                "from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com\n [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 5060A1E877\n for <dev@dpdk.org>; Thu,  9 Jul 2020 14:26:58 +0200 (CEST)",
                "from compute7.internal (compute7.nyi.internal [10.202.2.47])\n by mailout.nyi.internal (Postfix) with ESMTP id B96825C003F;\n Thu,  9 Jul 2020 08:26:57 -0400 (EDT)",
                "from mailfrontend2 ([10.202.2.163])\n by compute7.internal (MEProxy); Thu, 09 Jul 2020 08:26:57 -0400",
                "from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])\n by mail.messagingengine.com (Postfix) with ESMTPA id 55CE530653F0;\n Thu,  9 Jul 2020 08:26:56 -0400 (EDT)"
            ],
            "Subject": "Re: [dpdk-dev] [PATCH v5 1/2] mbuf: introduce accurate packet Tx\n\tscheduling",
            "In-Reply-To": "<1594223249-24629-1-git-send-email-viacheslavo@mellanox.com>",
            "Message-ID": "<10029338.slByJQ0L2h@thomas>",
            "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-Post": "<mailto:dev@dpdk.org>",
            "Cc": "dev@dpdk.org, matan@mellanox.com, rasland@mellanox.com,\n olivier.matz@6wind.com, bernard.iremonger@intel.com, mb@smartsharesystems.com",
            "Precedence": "list",
            "From": "Thomas Monjalon <thomas@monjalon.net>",
            "Content-Transfer-Encoding": "7Bit",
            "MIME-Version": "1.0",
            "References": "<1591771085-24959-1-git-send-email-viacheslavo@mellanox.com>\n <1594223249-24629-1-git-send-email-viacheslavo@mellanox.com>",
            "X-Original-To": "patchwork@inbox.dpdk.org",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Errors-To": "dev-bounces@dpdk.org",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "Content-Type": "text/plain; charset=\"us-ascii\"",
            "Delivered-To": "patchwork@inbox.dpdk.org",
            "Date": "Thu, 09 Jul 2020 14:26:54 +0200",
            "X-Mailman-Version": "2.1.15"
        }
    }
]