From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id AE09DA00C3; Fri, 7 Oct 2022 15:50:42 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 999094284D; Fri, 7 Oct 2022 15:50:42 +0200 (CEST) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by mails.dpdk.org (Postfix) with ESMTP id DB011427F6 for ; Fri, 7 Oct 2022 15:50:40 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id CF319320093A; Fri, 7 Oct 2022 09:50:37 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 07 Oct 2022 09:50:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1665150637; x= 1665237037; bh=CJicUXSMDxonIjhJfEQrHO+nooNBO8yTVa0F5Xe6kA4=; b=A Bg3bbe5Fs0y2yPsA8el9PWqK1mYBrmeUeNc86wtoimUuOXTb5jG68vbKVcB2G1ug 3K7TOKjdRItsLqne5u+fEIqNT+ZXKnLzW2MRSAyKXzsEbMu5R6snK6r0vJFBBMsx iCnp4vY4XS/8UI9lEa+psC4RHZJ1VPCQ/fme+rTbkk8uD4ztsa8E+O37maeWCXYs gF1IsPvHDnE8ZFP/FyQFv5UGykHPrdCljaUpN0+s7GmZuw3u1q0LRRTEEItAYCTu ffGtdwu8mSlsBm1vvnCzyPeu48nIy9iMhDJu98Wb00UPprmadUn4UebvlYTfElUr S8DtASdjoCu4NFjI55FVg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1665150637; x= 1665237037; bh=CJicUXSMDxonIjhJfEQrHO+nooNBO8yTVa0F5Xe6kA4=; b=W oxrNB2EVwKM1K3Xt4YihLLdY9loTVegrGpE5a8PppV1CDPlAQGDcodXuykmh0eiv vnbuILiLBzFHbHNa5O7YAQwNfCAGxX5ahRVAeABlhHS40jD4A6z3V9JN0Xs/LPGn A0m+KCsajRXslLcEO+PhGnYV4YejkRSmgOoKSvQFZYe5B86YVbaslyW7RQbBwX1q b9ZpOEenFZKRbdxDdiJmVvKtnUrpVkgxgvRIinSLsGTdwA8c3Wp2QWCm8M2i4qyT zY1uJOKLSFif5mRnkOD00QDArBC9Qb6ElCfMONYFPmae1wqXuWxTQaHOT/GOYVaB PAA/Cct7h06iODQemSxIQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeijedgieelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 7 Oct 2022 09:50:35 -0400 (EDT) From: Thomas Monjalon To: Shijith Thotton Cc: dev@dpdk.org, pbhagavatula@marvell.com, Shijith Thotton , Honnappa.Nagarahalli@arm.com, bruce.richardson@intel.com, jerinj@marvell.com, mb@smartsharesystems.com, olivier.matz@6wind.com, stephen@networkplumber.org, david.marchand@redhat.com Subject: Re: [PATCH v3 0/5] mbuf dynamic field expansion Date: Fri, 07 Oct 2022 15:50:33 +0200 Message-ID: <9051200.rMLUfLXkoz@thomas> In-Reply-To: References: <20220907134340.3629224-1-sthotton@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 21/09/2022 15:56, Shijith Thotton: > This is a continuation of the discussions[1] to add mbuf physical address field to dynamic field. > Previous version was to add PA field to dynamic field area based on the EAL IOVA mode option. It was > deemed unsafe as some components could still use the PA field without checking IOVA mode and there > are drivers which need PA to work. One suggestion was to make the IOVA mode check at compile time so > that drivers which need PA can be disabled during build. This series adds this new meson build > options. Second patch adds mbuf PA field to dynamic field on such builds. Last two patches enable > Marvell cnxk PMDs and software PMDs in IOVA as VA build as they work without PA field. Shijith, in case it was not clear, we can accept this change only in -rc1 closing today, and we didn't receive the expected v4 yet.