From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2CE0145644; Thu, 18 Jul 2024 13:48:39 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6B9DA42E94; Thu, 18 Jul 2024 13:48:33 +0200 (CEST) Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by mails.dpdk.org (Postfix) with ESMTP id 28398402D5 for ; Thu, 18 Jul 2024 13:48:29 +0200 (CEST) Received: from mail.maildlp.com (unknown [172.19.88.105]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4WPrdw0XPCznb2G; Thu, 18 Jul 2024 19:47:48 +0800 (CST) Received: from kwepemf500004.china.huawei.com (unknown [7.202.181.242]) by mail.maildlp.com (Postfix) with ESMTPS id C66B5140109; Thu, 18 Jul 2024 19:48:27 +0800 (CST) Received: from localhost.huawei.com (10.90.30.45) by kwepemf500004.china.huawei.com (7.202.181.242) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 18 Jul 2024 19:48:27 +0800 From: Jie Hai To: , , , , CC: , , Subject: [PATCH v2 0/3] bugfix about KEEP CRC offload Date: Thu, 18 Jul 2024 19:48:02 +0800 Message-ID: <20240718114806.577298-1-haijie1@huawei.com> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20240206011030.2007689-1-haijie1@huawei.com> References: <20240206011030.2007689-1-haijie1@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.90.30.45] X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To kwepemf500004.china.huawei.com (7.202.181.242) 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 From: Dengdui Huang For hns3 NIC, when KEEP_CRC offload is enabled, the CRC data is still be stripped in rare scenarios. Some users of hns3 are already using this feature. So driver has to recaculate packet CRC. In addition, in the mbuf, the data that exceeds the length specified by pkt_len is invalid. Therefore, if the packet contains CRC data, pkt_len should contain the CRC data length. However, almost of drivers supported KEEP CRC feature didn't add the CRC data length to pkt_len. This patch adds description for KEEP CRC offload. Dengdui Huang (3): ethdev: add description for KEEP CRC offload net/hns3: fix packet length do not contain CRC data length net/hns3: fix Rx packet without CRC data drivers/net/hns3/hns3_ethdev.c | 5 + drivers/net/hns3/hns3_ethdev.h | 23 +++++ drivers/net/hns3/hns3_rxtx.c | 134 ++++++++++++++++---------- drivers/net/hns3/hns3_rxtx.h | 3 + drivers/net/hns3/hns3_rxtx_vec.c | 3 +- drivers/net/hns3/hns3_rxtx_vec_neon.h | 19 ---- drivers/net/hns3/hns3_rxtx_vec_sve.c | 3 +- lib/ethdev/rte_ethdev.h | 6 ++ 8 files changed, 124 insertions(+), 72 deletions(-) -- 2.33.0