From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 665D9A04B5; Sun, 1 Nov 2020 10:15:31 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id AF9EF9AFD; Sun, 1 Nov 2020 10:15:29 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id D76467CAE for ; Sun, 1 Nov 2020 10:15:27 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 36CD95C00EB; Sun, 1 Nov 2020 04:15:27 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 01 Nov 2020 04:15:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= 2kR8tTw7ggzx0MNumX6hzerHZ4vHWCCxV49TIAwWyuo=; b=lM3ALI41HJVck02O fF5jg76rd0ZiEukQ7ZW2iyTsDQrwpxSmLoF1hNdYOQRvNQI4426lV5LKJM37+lOt Aj7qCt2QSyrGInnlvrEzGexbcyEV2dXxGv5Ix6gXYyC+sNKdKoaqvXsaVn4jBKQA 92fJm6pLhbrKSOtUkDSOd1w3WoGiSdOgl6v/eEvJSgHARRBZiIo+B7iDTt4RzEd+ FjBtGbSZzibIKuUCtaknmFm0352Fb0YwUNT+PBxuIjtiw77F0fBGnJs+Y9TmCGfu 5xPIvt8I/s7PeQWByyVDMRkne5Z6fSsqtZ6UnwKN5dIOaGf8IY9Rm8X0HFE2VOjJ 1ouEXw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=2kR8tTw7ggzx0MNumX6hzerHZ4vHWCCxV49TIAwWy uo=; b=VHJ5u3xxLNM1LH3GgfbNKm46t/1qIUYIfqhCRMelODALQDcPPkuWj33ue 2t/MY7HHnZLaH+HEoGJwO/PQapzYmosW6DxVwqDK9lKI4LTAsrkSY3rmq4HGzceb tHHzKnGCpyc6QV0BMPCTSMrzHkOpgEKdwL/T4+BQuJNeza/6aDZY0XF+LhDZGjXb k324I4WnBWYioeUXwYoWybSL5XdyFkLRZNuWMnlGFQLL7YV+nGL6mPqc9ga2qy0p X6yMFSMY0d2HePcC2AbohX8meUvIcMu+QixcsaN0LVUFqrcj3p8cy9vOgU1su4vT NSZstsBfiel4uF1VMSsCDZrNObA0Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrleelgddtvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeekteehtdeivefhieegjeelgedufeejheekkeetueevieeuvdevuedt jeevheevteenucfkphepjeejrddufeegrddvtdefrddukeegnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho nhdrnhgvth X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 01FB2328005A; Sun, 1 Nov 2020 04:15:24 -0500 (EST) From: Thomas Monjalon To: Jiawen Wu , Jian Wang , Ferruh Yigit Cc: dev@dpdk.org, david.marchand@redhat.com, bruce.richardson@intel.com, olivier.matz@6wind.com, andrew.rybchenko@oktetlabs.ru, akhil.goyal@nxp.com, jerinj@marvell.com Date: Sun, 01 Nov 2020 10:15:23 +0100 Message-ID: <2336246.PS5YtoHrA8@thomas> In-Reply-To: <5960b0cf-eb7a-af00-ae6a-86ad5e5db6eb@intel.com> References: <20201026052105.1561859-1-thomas@monjalon.net> <16204738.pLQXvH3U5b@thomas> <5960b0cf-eb7a-af00-ae6a-86ad5e5db6eb@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 01/11/2020 00:36, Ferruh Yigit: > 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. > >=20 > > Applied >=20 > The new txgbe driver in the next-net is also using =E2=80=98udata64=E2=80= =99, that also needs to=20 > be updated. cc'ed txgbe maintainer. That's a pity it did not take into account the deprecation notice. What kind of hack is it used for? Can it be simply removed to allow quick merging of the PMD?