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 E9C6141EB0; Thu, 16 Mar 2023 12:00:24 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DA89142D37; Thu, 16 Mar 2023 12:00:24 +0100 (CET) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by mails.dpdk.org (Postfix) with ESMTP id A1E2D42D32 for ; Thu, 16 Mar 2023 12:00:23 +0100 (CET) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailnew.nyi.internal (Postfix) with ESMTP id E085E58213D; Thu, 16 Mar 2023 07:00:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 16 Mar 2023 07:00:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type: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=fm2; t= 1678964422; x=1678971622; bh=h+bI98MHTrZ/+SNotDuZsi0uNTMAFe39Vz7 pN+9aBUU=; b=ugUcFXKujc3qNGBwbCpgNg7bgrmwwDbHa9DweAfr7iguh00pU2u fBW39Dh6jKlreCVl2JMrxl0dQ0wRoC+bP/X+U766jADWLpJh9PPHcyy5p74eNvBq BICU+WQer2dtnzDfCstc/RnVhnnnFTfqj8w1GhOAm4zslIUPAANljxO2Bg8QVIHW vr9y5StFNoIe1ltVcyPSE2cXr61jIQk/AoFoMJ1yXhW65ThRpH2z9x3gsoQaI7vV cMEcZhGZZK8NnsI/gBictUjWukRrNfBDn6FwsArkenm2Ou608nbxQxnmDO8h7/bz bsGag9cGZswT/0eXGRif2ry9nDNjYrzESgg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type: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=fm2; t= 1678964422; x=1678971622; bh=h+bI98MHTrZ/+SNotDuZsi0uNTMAFe39Vz7 pN+9aBUU=; b=uHQVVP4jnfuqf70WQe+98KsU8DW0k9NBr4HS4A6VpXt4piRZEPx NU8WU3H0GCDoXgfnGcCqly5vX8MmN0Ten+T7mVPYwKnjFuQUTBXSXgN+Nta23r4a 8ZTkurzvNMRAFiLGqdTW/QUXKC6EpZXvEhl6MY44qEwYOVFZHIn4q8B3hrQpE/re 5B9r8k5J6BAg6iYQxM/8WRW5SguV2lOA0kIOhO1vLkZdPmyXjRyDYH3aABrGB1Kl 8jjwimyAgel+AzLDIpB7JBAv1vM3HGBBII8SmzDLQ4L+HAwLlmajTF9ho4x4np2Q oRC7/095Dob/mmOsIl+7LaL6bhR+e0+wtCg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeftddgvdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtudenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeefhfejleeuvdevtddutdeutdevhfeijeethfffueejhfetuddu vedtkedtieekffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 16 Mar 2023 07:00:16 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: David Marchand , Bruce Richardson , Qi Zhang , Morten =?ISO-8859-1?Q?Br=F8rup?= , Shijith Thotton , Olivier Matz , Ruifeng Wang , Parav Pandit , Xueming Li , Tomasz Duszynski , Long Li , Nithin Dabilpuram , Kiran Kumar K , Sunil Kumar Kori , Satha Rao , Jingjing Wu , Beilei Xing , Ankur Dwivedi , Anoob Joseph , Tejasree Kondoj , Kai Ji , Pablo de Lara , Radha Mohan Chintakuntla , Veerasenareddy Burru , Kevin Laatz , Pavan Nikhilesh , Mattias =?ISO-8859-1?Q?R=F6nnblom?= , Liang Ma , Peter Mccarthy , Jerin Jacob , Harry van Haaren , "Artem V. Andreev" , Andrew Rybchenko , Ashwin Sekhar T K , Srikanth Yalavarthi , "John W. Linville" , Ciara Loftus , Chas Williams , "Min Hu (Connor)" , Yuying Zhang , Gaetan Rivet , Dongdong Liu , Yisen Zhuang , Konstantin Ananyev , Qiming Yang , Jakub Grajciar , Tetsuya Mukawa , Jakub Palider , Sachin Saxena , Hemant Agrawal , fengchengwen Subject: Re: [PATCH v3 1/5] build: clarify configuration without IOVA field in mbuf Date: Thu, 16 Mar 2023 12:00:15 +0100 Message-ID: <2273513.ElGaqSPkdT@thomas> In-Reply-To: <61879568-0fbc-5ce9-26c2-af5daae9afc4@huawei.com> References: <20230219115529.3260580-1-thomas@monjalon.net> <20230314142958.3479004-2-thomas@monjalon.net> <61879568-0fbc-5ce9-26c2-af5daae9afc4@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" 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 15/03/2023 02:56, fengchengwen: > On 2023/3/14 22:29, Thomas Monjalon wrote: > > The impact of the option "enable_iova_as_pa" is explained for users. > >=20 > > Also the code flag "RTE_IOVA_AS_PA" is renamed as "RTE_IOVA_IN_MBUF" > > in order to be more accurate (IOVA mode is decided at runtime), > > and more readable in the code. > >=20 > > Similarly the drivers are using the variable "require_iova_in_mbuf" > > instead of "pmd_supports_disable_iova_as_pa" with an opposite meaning. > > By default, it is assumed that drivers require the IOVA field in mbuf. > > The drivers which support removing this field have to declare themselve= s. > > Some bus drivers are declared compatible. > >=20 > > If the option "enable_iova_as_pa" is disabled, the unsupported drivers > > will be listed with the new reason text "requires IOVA in mbuf". > >=20 > > Suggested-by: Bruce Richardson > > Signed-off-by: Thomas Monjalon > > Reviewed-by: Bruce Richardson > > Acked-by: Morten Br=F8rup >=20 > Acked-by: Chengwen Feng Applied