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 C4F22A04FD; Mon, 1 Aug 2022 12:01:36 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id ADC2D41101; Mon, 1 Aug 2022 12:01:36 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id E81F54067B for ; Mon, 1 Aug 2022 12:01:35 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 92C495C00AC; Mon, 1 Aug 2022 06:01:33 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 01 Aug 2022 06:01:33 -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=1659348093; x= 1659434493; bh=C3tjeEVLSUyUQyK/5O72Yk95MMR7XJWdRZcoG7uAhYs=; b=I PzJODhLOlOY40b1AkjzIwiA2maKtSdSiTHsnSpCFQaHvfxXyIJLpQKfe0kks5ZGK 7A63eiEIdSZDVtvF722vcg5qYCDSW91VeVzO96JOqlICWs6cglnT5z9zcFmW3XvX b41AiAgi3GvjDkslYs71CzxJDs4E4hfJejBybR2/B2RRLmMoBSudCuCcHZ9LzguT c+gMZlbp1sNhD6rn+C480IuFeVFPOCkIT44wY6hhRSWAN6aSrBSA/T6s6M+hyypD wSzN0sKlBY7V2IwGnmhed7eFBHduKnDltJFQavcIO2L7hmg3LfDmO0hIEADomXKc RZoJvh+0LkfA8k4GX29Bw== 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=1659348093; x= 1659434493; bh=C3tjeEVLSUyUQyK/5O72Yk95MMR7XJWdRZcoG7uAhYs=; b=Q OIUHHkjna1V9XCN0q60VtuooGR9zK+qmd8NJJF8QfpVsDAiJZZ6jTxcRVIDE9+s+ njftdo1y+qOSVYHeaRyMeDrSy7kubhBCmLqHE7t64Oroe914yENJR2F/6fGlIJve F/N8Qvm9qnuMVTfmrxTLo8Ehui3QUwV5pYY1iaD4Q9F+khNHqeSQT7RxrN4MAX0f lah+RzjatQNuCslvwAq+fPGUHwtNZm6KjOtu4A4+Czn3uc2zvQvgrgcyIlqCkMKZ lI9wOsMgUj2/wRSDr/WBcsacQUHCMRcyw2zoq5JWphVbXPzsCt1AWhTkWNPu9L6u P2Sm0uG9mx/VYEd3dr8sg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvddvfedgvdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 1 Aug 2022 06:01:31 -0400 (EDT) From: Thomas Monjalon To: "Wang, YuanX" Cc: "andrew.rybchenko@oktetlabs.ru" , "Li, Xiaoyun" , "ferruh.yigit@xilinx.com" , "Singh, Aman Deep" , "dev@dpdk.org" , "Zhang, Yuying" , "Zhang, Qi Z" , "jerinjacobk@gmail.com" , "stephen@networkplumber.org" , "Wu, WenxuanX" , "Ding, Xuan" Subject: Re: [PATCH v9 1/4] ethdev: introduce protocol header API Date: Mon, 01 Aug 2022 12:01:29 +0200 Message-ID: <6334913.K2JlShyGXD@thomas> In-Reply-To: References: <20220303060136.36427-1-xuan.ding@intel.com> <3684735.UjfFaoq8vQ@thomas> 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 01/08/2022 09:09, Wang, YuanX: > Hi Thomas, > > Sorry so long to response your email. > > From: Thomas Monjalon > > 13/06/2022 12:25, wenxuanx.wu@intel.com: > > > From: Wenxuan Wu > > > > > > This patch added new ethdev API to retrieve supported protocol header > > > mask of a PMD, which helps to configure protocol header based buffer split. > > > > > > Signed-off-by: Wenxuan Wu > > > --- > > > +/** > > > + * @warning > > > + * @b EXPERIMENTAL: this API may change without prior notice > > > + * > > > + * Get supported header protocols to split supported by PMD. > > > + * The API will return error if the device is not valid. > > > + * > > > + * @param port_id > > > + * The port identifier of the device. > > > + * @param ptype > > > + * Supported protocol headers of driver. > > > > It doesn't say where to find the types. > > Please give the prefix. > > Sorry I didn't catch your point, are you referring the ptype should be composed of RTE_PTYPE_*? > Could you explain it in more detail? Yes just give to the user the required info to use the function. If ptype must be composed with RTE_PTYPE_*, it must be said. Thanks