From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5221AA046B for ; Tue, 23 Jul 2019 19:08:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 97DA21C07C; Tue, 23 Jul 2019 19:08:20 +0200 (CEST) Received: from mx0a-00103a01.pphosted.com (mx0a-00103a01.pphosted.com [67.231.144.234]) by dpdk.org (Postfix) with ESMTP id AB9251C06C for ; Tue, 23 Jul 2019 19:08:18 +0200 (CEST) Received: from pps.filterd (m0174892.ppops.net [127.0.0.1]) by mx0a-00103a01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x6NH4mmL007562; Tue, 23 Jul 2019 13:08:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ciena.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=06252019; bh=aJu36iLdZgeWo+nxYj7M07xivx+RjTTW8tnPcDM+vL0=; b=Qe2swoLO3X91S18JycZf+qdHTvdO2HPGsmqD0zo5JdJMqiS835Sh/ARu0DX5QeNxRrxH SJ/u/8UFHdgZRJC9VN61RvTL613q1F3GeXesJlIlIMHntPhttvldLlZ/XnTVP5k4o0JU kKEScWzIpohdZyMR7WEjfbrOyuNmRLmJnpRU25WYx/PCXQsdTBkIGNq0Sb0v9Rm6zIqn 2yNbhNpH4C8AhmMrDWyybvJioSlbEwwQmLqRBFcDZsiz+rIbfYuAjre/sVcaMplYL5dN kHYSx3B0f1EnLXAURmYXeaHF6GJNxf1y7EQWIlfFaMLAX1GQZPqNjZFPbgV6hWE7UsP7 vw== Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp2054.outbound.protection.outlook.com [104.47.49.54]) by mx0a-00103a01.pphosted.com with ESMTP id 2tx61rg3t0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 Jul 2019 13:08:17 -0400 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KMncu8J9xRE/TIaIC4lbQCox80rQLLztnpSqmjT/ktD0uXLELcWAJLfziCiD6VcCHKjT8MzsK1Rvkd5Kt5EOGZYm5dhrXaE5PB09h+7LgfdPUaS77jBFnCKntbc4pY5z3klVZKieLLpsobeq55VjPKYT/DIkzMWXdaiw60gm6HpZ4bXmIPJUs9q/GKgpbxCbL6jv3seMg5dVtZxQsmkBCnei+MZRl03qOUXAHR/OkyQaAfMqayPz12IF18/fjEckmU/6nhWNRohmWrQxoEQWPvzP/w2+Sni6Qb0nOEM9ACi9APqTtVbtMwk2MFjLjweHGAzeAqrCSL18SGfkDcvcwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aJu36iLdZgeWo+nxYj7M07xivx+RjTTW8tnPcDM+vL0=; b=T7N8VITj11NV9VifsEoBMfriHnM3ocZc0dcI/w+5CwKRTd1hLdPjqEBUjaRtTMP5Jbi+GNlaKgRM+Z17xtAPYX5fZuseVh6b7VR+LsR7SG5RPhBEOraS1eL2W5bOj+rN0etYgCame2J9Vm2jfU02L8A/XSB9TKW8FfR0FQbHONXxLDoipLbI5dRFT6sSVls1KmT9jzD+UZ51JIh9DlWf/gRwfGyseiDVmdrJw8UFGyR8MbAOFr/2ZD9dzve7wHe0d3enz2XinrH5c2PdTkM+vtsLGfoWUd2WqC1jcLUwG+MuCBGEBX5eNzWjo/ogHIqPdNur2YcNM2rIxJtGS4hgkw== ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=ciena.com;dmarc=pass action=none header.from=ciena.com;dkim=pass header.d=ciena.com;arc=none Received: from MWHPR04MB0592.namprd04.prod.outlook.com (10.173.49.145) by MWHPR04MB3742.namprd04.prod.outlook.com (10.172.170.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.17; Tue, 23 Jul 2019 17:08:14 +0000 Received: from MWHPR04MB0592.namprd04.prod.outlook.com ([fe80::a45f:7fde:28e4:8519]) by MWHPR04MB0592.namprd04.prod.outlook.com ([fe80::a45f:7fde:28e4:8519%7]) with mapi id 15.20.2094.013; Tue, 23 Jul 2019 17:08:14 +0000 From: "Bly, Mike" To: "Ananyev, Konstantin" , "'dev@dpdk.org'" Thread-Topic: [dpdk-dev] x552 transmit issue and rte_ethtool - rte_ethtool_get_regs() Thread-Index: AQHVQXAg9vjPmvftnkCp1nm+mPlQ5KbYbdCA Date: Tue, 23 Jul 2019 17:08:14 +0000 Message-ID: References: <2601191342CEEE43887BDE71AB9772580168A5A018@irsmsx105.ger.corp.intel.com> In-Reply-To: <2601191342CEEE43887BDE71AB9772580168A5A018@irsmsx105.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [165.225.50.165] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 73cfbaab-4d99-454b-40f5-08d70f905985 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7167020)(7193020); SRVR:MWHPR04MB3742; x-ms-traffictypediagnostic: MWHPR04MB3742: x-ms-exchange-purlcount: 2 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-forefront-prvs: 0107098B6C x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(39860400002)(346002)(376002)(396003)(13464003)(189003)(199004)(81166006)(305945005)(316002)(99286004)(26005)(66476007)(66446008)(86362001)(81156014)(11346002)(186003)(74316002)(14454004)(476003)(66946007)(110136005)(14444005)(229853002)(64756008)(66556008)(52536014)(71190400001)(71200400001)(446003)(7736002)(256004)(5660300002)(6246003)(76116006)(2906002)(486006)(55016002)(6306002)(53936002)(3846002)(33656002)(9686003)(966005)(66066001)(25786009)(53546011)(6506007)(55236004)(7696005)(68736007)(478600001)(76176011)(102836004)(8936002)(6436002)(6116002)(491001); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR04MB3742; H:MWHPR04MB0592.namprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: ciena.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: wkW1bFSVwKQbVcbR+iXc9YJASpqq5xPCcTQJBKa739yaT/aFP6qIOJVkjxxbz6g8YDD9N5zKsjr2rX9E8eIsxKOUzpu8CE/yCBhvtjrocn1PYwkVGFi0Qmp010IgnBDRbpq1xv5V/8OEMnFZMZDa8XdHhJqswXc8F9P8unxT+jXWzYeIWVqnjmh5eQQY2YdXbvCxAC+1ZM1FArfdHvsMxKzqNUgtv+YG3QGVn9zXDXwZEr6L8GXcSB3GbfaJlkavQasW5fZKOzCIKCEK+zcwoMKOx8mM84rn7HV7PyvhhOq9kBG2vPKsOgO8X40cQ/6D/fovooN+37TJxPgcVNdiwin2D6AedoVHo2Q5GgtFeIkuZS1Kxa4+YU2/Kx90UCQiUMgorZXyo938th1CrwgTI4sr9cd0EleZyb+KIIvFRi8= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: ciena.com X-MS-Exchange-CrossTenant-Network-Message-Id: 73cfbaab-4d99-454b-40f5-08d70f905985 X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jul 2019 17:08:14.5825 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 457a2b01-0019-42ba-a449-45f99e96b60a X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: mbly@ciena.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR04MB3742 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-07-23_07:2019-07-23,2019-07-23 signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxscore=0 clxscore=1011 priorityscore=1501 malwarescore=0 suspectscore=0 spamscore=0 adultscore=0 lowpriorityscore=0 bulkscore=0 mlxlogscore=999 impostorscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1907230171 Subject: Re: [dpdk-dev] x552 transmit issue and rte_ethtool - rte_ethtool_get_regs() X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Konstantin, Thank you for the prompt reply on this posting. In looking at the single us= e-case in test-pmd's csumonly.c, it would seem prepare + retry_enabled may = have some shortcomings as currently coded when nb_prep < nb_rx. Has anyone = looked at this? I happened to notice this when looking for a reference for = how it is expected to be used. It would seem nb_rx should be replaced with = nb_prep in the retry code. I think the rest of the code should "just work" = from there. Thoughts? Regards, Mike -----Original Message----- From: Ananyev, Konstantin =20 Sent: Tuesday, July 23, 2019 9:03 AM To: Bly, Mike ; 'dev@dpdk.org' Subject: [**EXTERNAL**] RE: [dpdk-dev] x552 transmit issue and rte_ethtool = - rte_ethtool_get_regs() >=20 > Hello, >=20 > We are chasing an interesting NIC transmit issue where after some=20 > period of time with normal operation the NIC enters a state where it=20 > refuses to transmit frames from our DPDK application via rte_eth_tx_burst= (). All indications are the port is up and otherwise operational and is sti= ll receiving traffic. It simply refuses to transmit anymore. >=20 > Our application is running DPDK 17.05.1. In digging through the email=20 > archives, this appears to be related to the following posts, as we see th= e same nb_free =3D 0 and IXGBE_ADVTXD_STAT_DD not set problems they describ= e: > http://mails.dpdk.org/archives/dev/2017-August/073240.html > http://inbox.dpdk.org/dev/b704af91-dcc6-4481-a54c-3e174b744d17.h.liu@a > libaba-inc.com/ >=20 > Having not seen any resolution on the above DPDK posts and after a=20 > number of other investigative steps, we incorporated the rte_ethtool=20 > lib to provide the ability to dump the NIC register set via=20 > rte_ethtool_get_regs() in the hopes that perhaps there would be something= there in a status register to point us in the right direction. The questio= n now is what is the best way to check the register contents dumped to the = binary output file this API creates, for the x552 NIC? Does anyone know if = a decoder script exists? >=20 > Other ideas to pursue? It is hard to tell without any other information, but sometimes that happen= s when user tries to TX malformed packet. Might be worth to try using rte_eth_tx_prepare() inside your app. It does some sanity checks to prevent such situations, especially when RTE_= LIBRTE_ETHDEV_DEBUG is on. Konstantin=20