From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 7A807A0AC5 for ; Fri, 3 May 2019 01:22:59 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 735A95F17; Fri, 3 May 2019 01:22:58 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 989CD5B12 for ; Fri, 3 May 2019 01:22:56 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id ABEF920A14; Thu, 2 May 2019 19:22:54 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 02 May 2019 19:22:54 -0400 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=mesmtp; bh=Ih1+ghTpXoiMI90B2vEIClLSe8Y14ykJFNqEVU4m8m4=; b=QzhM1G3JnwG7 7xDk3eol57gKGPn8d9YapF6R09MLXVUMcsH6G85XRiKCAlL9Y15JICq/vdJ1uSve /Dr2EdmnwtJ/7GTux2uIROaO1cp8xrAbA02cwwjqwcVGz6cPZkxSQRf8LEsEGbjD aqD7CvK8S7MaVJmWbwEtrlP2H241h10= 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=fm2; bh=Ih1+ghTpXoiMI90B2vEIClLSe8Y14ykJFNqEVU4m8 m4=; b=f6jQv6wYvIqodMS2K0ss88vXrrMe5+A7TB/ItvTwK7dEQuWqbM6d8jmVT wqDHGWqppxXY+6tc6/VunYusxvqoypZvO9nTIVdjtNMTvUBzkkP9LI5z0XCDUoq6 6oblyaXmG5rC9JeCeotK6+hAN8Q6PJUL1OpEOHJY/DAiHxFjPEJ9odHPuAylHFDy xCgc6i0Gjc0ayJyuvDlCj1EReQS2oByvHBWgM5i0tnmAAYSEi07o7Gpz+WCDAk/p R350URgWQWzSvMCqMQywRyn9BkmSTdmiqGPrdexkPFkBpvfJxv3y1zqz0UyDgBrc QPGU4dNuWVBAMlz0w//jsdWjXMGuQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrjedtgddvtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 8F545E4382; Thu, 2 May 2019 19:22:53 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org Date: Fri, 03 May 2019 01:22:52 +0200 Message-ID: <2511331.Laj1Cp0Ard@xps> In-Reply-To: <20190425094019.11430-1-shreyansh.jain@nxp.com> References: <20190103112932.4415-1-shreyansh.jain@nxp.com> <20190425094019.11430-1-shreyansh.jain@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v2] examples/l3fwd: support separate buffer pool per port 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" Message-ID: <20190502232252.UJHz4SQ6HVg8RZmGsmyLR5mwSmFTGQTaoEyn_hwV9dw@z> 25/04/2019 11:40, Shreyansh Jain: > Traditionally, only a single buffer pool per port > (or, per-port-per-socket) is created in l3fwd application. > > If separate pools are created per-port, it might lead to gain in > performance as packet alloc/dealloc requests would be isolated > across ports (and their corresponding lcores). > > This patch adds an argument '--per-port-pool' to the l3fwd application. > By default, old mode of single pool per port (split on sockets) is > active. > > L3fwd user guide is also updated by this patch. > > Signed-off-by: Shreyansh Jain > Acked-by: Ruifeng Wang Applied, thanks