From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id B4126A0562;
	Fri, 19 Mar 2021 13:13:28 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 37B5D40143;
	Fri, 19 Mar 2021 13:13:28 +0100 (CET)
Received: from szxga05-in.huawei.com (szxga05-in.huawei.com [45.249.212.191])
 by mails.dpdk.org (Postfix) with ESMTP id 275134003F
 for <dev@dpdk.org>; Fri, 19 Mar 2021 13:13:25 +0100 (CET)
Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.58])
 by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4F22mK3NWkzPkdf;
 Fri, 19 Mar 2021 20:10:57 +0800 (CST)
Received: from [10.67.103.128] (10.67.103.128) by
 DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id
 14.3.498.0; Fri, 19 Mar 2021 20:13:20 +0800
To: "dev@dpdk.org" <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>,
 Thomas Monjalon <thomas@monjalon.net>
From: "Min Hu (Connor)" <humin29@huawei.com>
Message-ID: <3ddef567-d7ee-5364-cf42-81118a7153ee@huawei.com>
Date: Fri, 19 Mar 2021 20:13:20 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.3.1
MIME-Version: 1.0
Content-Type: text/plain; charset="gbk"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.67.103.128]
X-CFilter-Loop: Reflected
Subject: [dpdk-dev] Questions about keeping CRC
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <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>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi, all,
	DPDK has introduced one offload: DEV_RX_OFFLOAD_KEEP_CRC. It means that 
the device has the ablility of keeping CRC£¨four bytes at the end of 
packet£©of packet in RX.
	In common scenarios, When one packet enter into NIC device, NIC
will check the CRC and then strip the CRC£¬at last send the packet into 
the buffer.
	So my question is:
	 why the DEV_RX_OFFLOAD_KEEP_CRC is introduced into DPDK?  I think that 
when the packet enter into the NIC, the CRC will has no significance to 
APP. Or is there any scenarios that CRC is useful for APP£¿
	Thanks for your reply.