From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 185D637A8 for ; Tue, 2 Apr 2019 02:06:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 93CD022178; Mon, 1 Apr 2019 20:06:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 01 Apr 2019 20:06:46 -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=KGgDjPkv9J32Pn2JdEcrt+a6p6E/+ywYkDj8TFDfSCU=; b=r5SoXMvGyLoQ zpLqsPyGAoxhDlhbU067HFX1LqsykGiPaAoHL3/gK0d8A44g0FxpDzVD1H5emK4R zsdCOjUcLlR/krfSwn4PAxg5lUPJRB38m4li0Vl9+rDDOtNwjxe9E4i+WzPoCNoa M6ZigYCUsRLMPGsbRyuP1/D87VLOeC8= 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=KGgDjPkv9J32Pn2JdEcrt+a6p6E/+ywYkDj8TFDfS CU=; b=I/GOjJYopvnggaPRDVZHSqa+XQ+Ah7KnFrwv3D5HUVodeKr/ANsVOSLZx PjwelZUGxO7rCgcNI9dSEtPXpQ9PCgIomaCxfuvzDflfyUTZG+2nv334rL23S4Cg eg+jzVUPNR5aXexSmBCT3v1qLYIbpbMRWyPLSPQHmAf9pT9roq0uJPMOsE86Jj58 XMopyFsIIQFgSBljXC5EW0rcAwSqbWTLMarFN93zJWQpHRhBiiqrkUcHORrOijEX OFA8kcNGBzxyLzVed7+bWJxSTjoaOiivQLuSKZ6n3eVN+9vtwXGY1rlNhT0aoNOh mzl24sdAjVycByakMEPCNxHG1k93g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrleehgddvkecutefuodetggdotefrodftvf 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 8434D1030F; Mon, 1 Apr 2019 20:06:42 -0400 (EDT) From: Thomas Monjalon To: David Hunt Cc: dev@dpdk.org, anatoly.burakov@intel.com, liang.j.ma@intel.com Date: Tue, 02 Apr 2019 02:06:41 +0200 Message-ID: <2066148.uFblHQ0ktz@xps> In-Reply-To: <20190401161441.29328-2-david.hunt@intel.com> References: <20190401153044.39273-1-david.hunt@intel.com> <20190401161441.29328-1-david.hunt@intel.com> <20190401161441.29328-2-david.hunt@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v5 2/2] examples/distributor: detect high frequency cores 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: , X-List-Received-Date: Tue, 02 Apr 2019 00:06:47 -0000 01/04/2019 18:14, David Hunt: > The distributor application is bottlenecked by the distributor core, > so if we can give more frequency to this core, then the overall > performance of the application may increase. > > This patch uses the rte_power_get_capabilities() API to query the > cores provided in the core mask, and if any high frequency cores are > found (e.g. Turbo Boost is enabled), we will pin the distributor > workload to that core. > > Signed-off-by: Liang Ma > Signed-off-by: David Hunt > Reviewed-by: Anatoly Burakov Series applied, thanks 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 45EB0A0679 for ; Tue, 2 Apr 2019 02:06:50 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8DF374C8D; Tue, 2 Apr 2019 02:06:48 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 185D637A8 for ; Tue, 2 Apr 2019 02:06:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 93CD022178; Mon, 1 Apr 2019 20:06:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 01 Apr 2019 20:06:46 -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=KGgDjPkv9J32Pn2JdEcrt+a6p6E/+ywYkDj8TFDfSCU=; b=r5SoXMvGyLoQ zpLqsPyGAoxhDlhbU067HFX1LqsykGiPaAoHL3/gK0d8A44g0FxpDzVD1H5emK4R zsdCOjUcLlR/krfSwn4PAxg5lUPJRB38m4li0Vl9+rDDOtNwjxe9E4i+WzPoCNoa M6ZigYCUsRLMPGsbRyuP1/D87VLOeC8= 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=KGgDjPkv9J32Pn2JdEcrt+a6p6E/+ywYkDj8TFDfS CU=; b=I/GOjJYopvnggaPRDVZHSqa+XQ+Ah7KnFrwv3D5HUVodeKr/ANsVOSLZx PjwelZUGxO7rCgcNI9dSEtPXpQ9PCgIomaCxfuvzDflfyUTZG+2nv334rL23S4Cg eg+jzVUPNR5aXexSmBCT3v1qLYIbpbMRWyPLSPQHmAf9pT9roq0uJPMOsE86Jj58 XMopyFsIIQFgSBljXC5EW0rcAwSqbWTLMarFN93zJWQpHRhBiiqrkUcHORrOijEX OFA8kcNGBzxyLzVed7+bWJxSTjoaOiivQLuSKZ6n3eVN+9vtwXGY1rlNhT0aoNOh mzl24sdAjVycByakMEPCNxHG1k93g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrleehgddvkecutefuodetggdotefrodftvf 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 8434D1030F; Mon, 1 Apr 2019 20:06:42 -0400 (EDT) From: Thomas Monjalon To: David Hunt Cc: dev@dpdk.org, anatoly.burakov@intel.com, liang.j.ma@intel.com Date: Tue, 02 Apr 2019 02:06:41 +0200 Message-ID: <2066148.uFblHQ0ktz@xps> In-Reply-To: <20190401161441.29328-2-david.hunt@intel.com> References: <20190401153044.39273-1-david.hunt@intel.com> <20190401161441.29328-1-david.hunt@intel.com> <20190401161441.29328-2-david.hunt@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v5 2/2] examples/distributor: detect high frequency cores 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: <20190402000641.tKs735dZmKErtRtvqwRHwQgHbbE5uAPQ8v7cWL0Fa40@z> 01/04/2019 18:14, David Hunt: > The distributor application is bottlenecked by the distributor core, > so if we can give more frequency to this core, then the overall > performance of the application may increase. > > This patch uses the rte_power_get_capabilities() API to query the > cores provided in the core mask, and if any high frequency cores are > found (e.g. Turbo Boost is enabled), we will pin the distributor > workload to that core. > > Signed-off-by: Liang Ma > Signed-off-by: David Hunt > Reviewed-by: Anatoly Burakov Series applied, thanks