From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A0917A04DC;
	Sun,  1 Nov 2020 00:37:07 +0100 (CET)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id DC1485B38;
	Sun,  1 Nov 2020 00:37:05 +0100 (CET)
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31])
 by dpdk.org (Postfix) with ESMTP id 26C595ABB
 for <dev@dpdk.org>; Sun,  1 Nov 2020 00:37:03 +0100 (CET)
IronPort-SDR: 8QPRmC1VElCr3flHknnxoiFK7LoOliGtfm3nBFQhDVg0uw6X9Xt1Y4gdLTZtSAUFvNGQPWHlPw
 z/s+MApOIgRQ==
X-IronPort-AV: E=McAfee;i="6000,8403,9791"; a="230393138"
X-IronPort-AV: E=Sophos;i="5.77,439,1596524400"; d="scan'208";a="230393138"
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 31 Oct 2020 16:37:01 -0700
IronPort-SDR: XvdU8wbWAbzALZcQAO7Ha1Pi+1wpgB4U8rQ2YLrYh1x9oey00cUcp5ORONwiCtAezcp5aoEZpW
 Oj9pK2+7YW/w==
X-IronPort-AV: E=Sophos;i="5.77,439,1596524400"; d="scan'208";a="352277634"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.218.27])
 ([10.213.218.27])
 by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 31 Oct 2020 16:36:59 -0700
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org,
 Jiawen Wu <jiawenwu@trustnetic.com>, Jian Wang <jianwang@trustnetic.com>
Cc: david.marchand@redhat.com, bruce.richardson@intel.com,
 olivier.matz@6wind.com, andrew.rybchenko@oktetlabs.ru, akhil.goyal@nxp.com,
 jerinj@marvell.com
References: <20201026052105.1561859-1-thomas@monjalon.net>
 <20201030174441.1076264-1-thomas@monjalon.net> <16204738.pLQXvH3U5b@thomas>
From: Ferruh Yigit <ferruh.yigit@intel.com>
Message-ID: <5960b0cf-eb7a-af00-ae6a-86ad5e5db6eb@intel.com>
Date: Sat, 31 Oct 2020 23:36:55 +0000
MIME-Version: 1.0
In-Reply-To: <16204738.pLQXvH3U5b@thomas>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [dpdk-dev] [PATCH v6 00/15] remove mbuf userdata
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
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>

On 10/31/2020 3:07 PM, Thomas Monjalon wrote:
> 30/10/2020 18:44, Thomas Monjalon:
>> The mbuf field userdata (aliased as udata64)
>> was announced to be removed for two reasons:
>>    - applications, libraries and drivers used the same field
>>      for different purposes, with a risk of usage conflict.
>>    - this field always used 8 bytes even if unneeded
>>
>> Some dynamic fields are created when needed to replace
>> the big static userdata field.
>> As a consequence, 8 bytes can be re-allocated to dynamic fields.
>>
>> This mbuf layout change is important to allow adding more features
>> (consuming more dynamic fields) during the next year.
> 
> Applied
> 

The new txgbe driver in the next-net is also using ‘udata64’, that also needs to 
be updated. cc'ed txgbe maintainer.