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 AF19BA04FF;
	Tue, 24 May 2022 16:58:50 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 9F4FE4281F;
	Tue, 24 May 2022 16:58:50 +0200 (CEST)
Received: from mail-108-mta146.mxroute.com (mail-108-mta146.mxroute.com
 [136.175.108.146])
 by mails.dpdk.org (Postfix) with ESMTP id 27A0340140
 for <dev@dpdk.org>; Tue, 24 May 2022 16:58:49 +0200 (CEST)
Received: from filter006.mxroute.com ([140.82.40.27]
 140.82.40.27.vultrusercontent.com)
 (Authenticated sender: mN4UYu2MZsgR)
 by mail-108-mta146.mxroute.com (ZoneMTA) with ESMTPSA id
 180f693d750000c327.001 for <dev@dpdk.org>
 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256);
 Tue, 24 May 2022 14:58:45 +0000
X-Zone-Loop: 71f19f2edb9997572a5d12fdcb463c3b33a21b90f3fa
X-Originating-IP: [140.82.40.27]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ashroe.eu; 
 s=x;
 h=Content-Type:MIME-Version:Message-ID:Date:In-reply-to:Subject:Cc:To:
 From:References:Sender:Reply-To:Content-Transfer-Encoding:Content-ID:
 Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
 :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
 List-Post:List-Owner:List-Archive;
 bh=WrcyO/NnwJM/9osv17yapduNH7Q5PF8Kh8z1ajBK9YM=; b=JPzjORMr7YMEPAR+WxHWE58WSS
 V2MAh487Nj2xq6f1RNuWBZIT82QUQf7vwI8HKHHDMVCq6Jf3AOacSMbER82lQg8hUuC29Bm/8azTf
 4xyL96GtQinUhMaCrCbq4NzxNavWVNCLWx4t3AnCpF5cAEuVKXnG4w32ZgUDn0NQK4nSB3xOqflxx
 QjocSXZ79XEkj367PR16zQqxVejk4PHx/onumK14UO9/tyum5v0/eQaZm5W2fFEWnsZgPBmFEFkNq
 Sv55E2nFl2oP36eDIY33FVgJHrUEE4o8rqeUI/2P5e9pHAJmjo5ZqpSw6/Xb0jCPf2xDj7zDqUhoJ
 nw6D2BcQ==;
References: <20220523142016.44451-1-xuan.ding@intel.com>
User-agent: mu4e 1.4.15; emacs 27.1
From: Ray Kinsella <mdr@ashroe.eu>
To: xuan.ding@intel.com
Cc: thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru,
 stephen@networkplumber.org, mb@smartsharesystems.com, dev@dpdk.org
Subject: Re: [PATCH] doc: announce header split deprecation
In-reply-to: <20220523142016.44451-1-xuan.ding@intel.com>
Date: Tue, 24 May 2022 15:58:42 +0100
Message-ID: <87mtf7yo2l.fsf@mdr78.vserver.site>
MIME-Version: 1.0
Content-Type: text/plain
X-AuthUser: mdr@ashroe.eu
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


xuan.ding@intel.com writes:

> From: Xuan Ding <xuan.ding@intel.com>
>
> RTE_ETH_RX_OFFLOAD_HEADER_SPLIT offload was introduced some time ago to
> substitute bit-field header_split in struct rte_eth_rxmode. It allows
> to enable header split offload with the header size controlled using
> split_hdr_size in the same structure.
>
> Right now, no single PMD actually supports RTE_ETH_RX_OFFLOAD_HEADER_SPLIT
> with above definition. Many examples and test apps initialize the field
> to 0 explicitly. The most of drivers simply ignore split_hdr_size since
> the offload is not advertised, but some double-check that its value is 0.
>
> So the RTE_ETH_RX_OFFLOAD_HEADER_SPLIT and split_header_size field
> will be removed in DPDK 22.11.
>
> Signed-off-by: Xuan Ding <xuan.ding@intel.com>


Acked-by: Ray Kinsella <mdr@ashroe.eu>