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 10B3EA034C; Tue, 18 Jan 2022 17:53:52 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9B67F4067C; Tue, 18 Jan 2022 17:53:51 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 5FCDB4014E for ; Tue, 18 Jan 2022 17:53:50 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CDA0C5C05D9; Tue, 18 Jan 2022 11:53:48 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 18 Jan 2022 11:53:48 -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=fm3; bh= PUv+OIMRSHqUeQX3aD7yCIwU6D2Bf19OnXosoNcRngo=; b=VbtnH/QPY3Zrv3n5 bLNwk8l0Qaq1nyzp22FOK18OAwD/wUafcfVr/2WTEpbw4xYZMadKFgXYHmgg3dwA yupxd1y7lMcA3jfzhcvcQAHZ2FtUVsDHrfoG9Qc27qUUV8WXWdSEaxfM2txynQ6c hx5uFsIHPdsrnIAeo24AhiFP4cTI27T/OLTPdYb1OU8JiLCPihSMFMOlZWpjPP4i PPzichB79/VwIcl1QXfJZVf4zsjl3W2xO7gyOCo9bGyJI2YA3N+zB7TIu8U8k62u FiWnIPejN+qeqE7cTXyRoDZgV9BqT0xo1y3JzuukbGXmZ55Y7qQrehX9Leg2vDV1 tXlFfw== 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=PUv+OIMRSHqUeQX3aD7yCIwU6D2Bf19OnXosoNcRn go=; b=ORpIJlkvkrR9lqBIKsNXt+2xPeDL/uin86/Vj0PGjP1SE5V9Yg9aSEw6+ Fq/wwPjPGEKE9I0McDfG7dkFP6MHcH/uGmZzBrx4uc1eJGcUH+OSPcsPmaOWPka/ /YetX4L89KVxirTg08fFnTP5rOGARm9nm1MOpM1YHnUKl3Oltm4YWka+E8Qe6UqD nKV/+9YAboCd7Ja3tOG4NtFAZYExZnzh81oWlQltIjnspksVwjcxHURlXgIPpkcz xDqEWUsnksJKBPLeYaK0gvD9/kMa2S2VmZkAbXckMO5/zlnwa4KK6PnzA0cEvAoT Dyn6X19C3JCL5sFdzyvTS7r6xUuFg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudefgdelgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthhqredttddtudenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeefgeffiefhfeettdfhvdfgteekffffudekvedtvedtvdfgveeuudev gedvgeegtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 Jan 2022 11:53:45 -0500 (EST) From: Thomas Monjalon To: Feifei Wang , Morten =?ISO-8859-1?Q?Br=F8rup?= , Ferruh Yigit Cc: dev@dpdk.org, nd , Andrew Rybchenko , Qi Zhang , Beilei Xing Subject: Re: =?UTF-8?B?5Zue5aSNOg==?= [RFC PATCH v1 0/4] Direct re-arming of buffers on receive side Date: Tue, 18 Jan 2022 17:53:42 +0100 Message-ID: <2898883.0vhOF50zNu@thomas> In-Reply-To: <996c2239-1a3f-2fbd-d8af-40c3e17f375a@intel.com> References: <20211224164613.32569-1-feifei.wang2@arm.com> <996c2239-1a3f-2fbd-d8af-40c3e17f375a@intel.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 [quick summary: ethdev API to bypass mempool] 18/01/2022 16:51, Ferruh Yigit: > On 12/28/2021 6:55 AM, Feifei Wang wrote: > > Morten Br=F8rup : > >> The patch provides a significant performance improvement, but I am > >> wondering if any real world applications exist that would use this. On= ly a > >> "router on a stick" (i.e. a single-port router) comes to my mind, and = that is > >> probably sufficient to call it useful in the real world. Do you have a= ny other > >> examples to support the usefulness of this patch? > >> > > One case I have is about network security. For network firewall, all pa= ckets need > > to ingress on the specified port and egress on the specified port to do= packet filtering. > > In this case, we can know flow direction in advance. >=20 > I also have some concerns on how useful this API will be in real life, > and does the use case worth the complexity it brings. > And it looks too much low level detail for the application. That's difficult to judge. The use case is limited and the API has some severe limitations. The benefit is measured with l3fwd, which is not exactly a real app. Do we want an API which improves performance in limited scenarios at the cost of breaking some general design assumptions? Can we achieve the same level of performance with a mempool trick?