From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3] net/mlx4: support CRC strip toggling Date: Wed, 28 Mar 2018 15:19:18 +0100 Message-ID: References: <1521477410-8936-1-git-send-email-ophirmu@mellanox.com> <20180326115452.GF4011@6wind.com> <2388926.RzC4zprzFL@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Ophir Munk , "dev@dpdk.org" , Olga Shern To: Shahaf Shuler , Thomas Monjalon , Adrien Mazarguil Return-path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 6E14A2C54 for ; Wed, 28 Mar 2018 16:19:22 +0200 (CEST) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 3/28/2018 7:03 AM, Shahaf Shuler wrote: > Monday, March 26, 2018 3:31 PM, Thomas Monjalon: >> 26/03/2018 13:54, Adrien Mazarguil: >>> On Mon, Mar 26, 2018 at 12:38:22PM +0100, Ferruh Yigit wrote: >>>> On 3/25/2018 9:19 PM, Ophir Munk wrote: >>>>> Previous to this commit mlx4 CRC stripping was executed by default >>>>> and there was no verbs API to disable it. >>>> >>>> Are you aware of the discussion about CRC [1]? Is this patch compatible >> with plans? >>>> >>>> [1] >>>> >> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fd >>>> >> pdk.org%2Fdev%2Fpatchwork%2Fpatch%2F36415%2F&data=02%7C01%7Csh >> ahafs% >>>> >> 40mellanox.com%7C90c78c02ec954cc1dfda08d59315619f%7Ca652971c7d2e4 >> d9b >>>> >> a6a4d149256f461b%7C0%7C0%7C636576642435977344&sdata=broGz4U2Kw1 >> u9xJk >>>> t%2FryP7j2CU9XN0GnM5jsUxHwiNg%3D&reserved=0 >>> >>> I wasn't aware of this notice. Looks like it makes this patch >>> unnecessary since mlx4 always strip by default; this patch makes it >>> configurable at will and only exposes the capability when HW supports >>> its configuration (i.e. the ability to leave CRC inside mbuf). >>> >>> We'd just need mlx4 to not expose DEV_RX_OFFLOAD_CRC_STRIP at all in >>> mlx5_get_rx_queue_offloads() in order to fully comply. >>> >>> I leave it up to you, I don't mind if we include this patch only to >>> revert it later when we finally get rid of DEV_RX_OFFLOAD_CRC_STRIP. >> >> A new flag to keep CRC will be introduced. >> We will need toggling anyway. > > Do we have such CRC flag already? If not I will include this patch and we revert/adjust it when the new flag will be introduced. Patch sent recently [1] but not merged yet, your review may help there :) [1] https://dpdk.org/dev/patchwork/patch/36416/ > >> >> >