From patchwork Mon Jan 10 03:20:14 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yunjian Wang X-Patchwork-Id: 105702 X-Patchwork-Delegate: qi.z.zhang@intel.com Return-Path: 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]) by inbox.dpdk.org (Postfix) with ESMTP id B17C9A04AD; Mon, 10 Jan 2022 04:20:23 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 356B7406A2; Mon, 10 Jan 2022 04:20:23 +0100 (CET) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by mails.dpdk.org (Postfix) with ESMTP id 9C86F4013F; Mon, 10 Jan 2022 04:20:21 +0100 (CET) Received: from dggpemm500022.china.huawei.com (unknown [172.30.72.54]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4JXJvh4jncz9s5X; Mon, 10 Jan 2022 11:19:12 +0800 (CST) Received: from dggpemm100016.china.huawei.com (7.185.36.192) by dggpemm500022.china.huawei.com (7.185.36.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Mon, 10 Jan 2022 11:20:14 +0800 Received: from dggpemm500008.china.huawei.com (7.185.36.136) by dggpemm100016.china.huawei.com (7.185.36.192) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Mon, 10 Jan 2022 11:20:14 +0800 Received: from dggpemm500008.china.huawei.com ([7.185.36.136]) by dggpemm500008.china.huawei.com ([7.185.36.136]) with mapi id 15.01.2308.020; Mon, 10 Jan 2022 11:20:14 +0800 From: wangyunjian To: "dev@dpdk.org" , "users@dpdk.org" , "qiming.yang@intel.com" , "qi.z.zhang@intel.com" CC: Huangshaozhang , dingxiaoxiong Subject: [dpdk-dev] [dpdk-users] A question about the link status of the intel E810 nic can not be up? Thread-Topic: [dpdk-dev] [dpdk-users] A question about the link status of the intel E810 nic can not be up? Thread-Index: AdgF0Pn/6qGT4vxjTVSzS48+AOJr4g== Date: Mon, 10 Jan 2022 03:20:14 +0000 Message-ID: <41f0c2c9f77348fbb22dad35ef155536@huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.174.242.157] MIME-Version: 1.0 X-CFilter-Loop: Reflected X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi, All: I am using Intel E810 with DPDK v21.11 to create a dpdkbond but there is a probability that the failure will occur. During the test, the bonding is repeatedly added and deleted. Sometimes, the link status of the NIC is Down. And if call ice_dev_set_link_up again, the link status of the NIC can be recovered. Alternatively, the problem can be avoided by modifying the ice pmd driver. diff --git a/drivers/net/ice/ice_ethdev.c b/drivers/net/ice/ice_ethdev.c index 13a7a9702a..fcd22e20a5 100644 --- a/drivers/net/ice/ice_ethdev.c +++ b/drivers/net/ice/ice_ethdev.c @@ -3604,7 +3604,7 @@ ice_dev_start(struct rte_eth_dev *dev) ice_dev_set_link_up(dev); /* Call get_link_info aq commond to enable/disable LSE */ - ice_link_update(dev, 0); + ice_link_update(dev, 1); pf->adapter_stopped = false;