From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C28F5A0524; Mon, 7 Dec 2020 10:46:13 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2B7A2F72; Mon, 7 Dec 2020 10:46:12 +0100 (CET) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) by dpdk.org (Postfix) with ESMTP id 1BA4DE07 for ; Mon, 7 Dec 2020 10:46:10 +0100 (CET) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 2FD2EE96; Mon, 7 Dec 2020 04:46:05 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 07 Dec 2020 04:46:05 -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=fm2; bh= P2Xxs0ApXbDVTWrqVte9GUs9x4XKA7zCgq3IBLp9nIE=; b=JP6NpB3hUUTAkNAl MCiuuP+rYEdgOaFrp6yclvIUKikyZbBLFbqtgsIo8PqFyi0VtXFwvj7OKVHTA/Jz aE4g0JPyUx5csLAea2NU3mjYvd0jQMvzSidIOid/L0NkQLhOUurgkIio99K1rjzT MbGHrBmhWwO2kWA0Aj/BWP55uDforyU/zhUNkuAWcwv61qVQoAYT9+g9b1HcmwDr srYMVjVu5v1caicIloRaYq/NFwCYzn02Bs3iKflBsSwBsrmpICHzMg/dtPt6pbCR tj5C9OKFZQqY+zQPSlev4neZVujZdlWtme26++wKMsvVIK7JcWPbsg05O6Ss6Clk 3Df9ww== 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=P2Xxs0ApXbDVTWrqVte9GUs9x4XKA7zCgq3IBLp9n IE=; b=CT9CZ/i8Tb9dOB3tQNuj/6qOcOwpCPkTY71CNnqITCEC7RclSyBx0zADO ZEnOyzXnXPiJqlMbNcd5GD1+XdvoWHV4zfXm3qDj7+XEfykqJQU2En2NeM64z5zU TQOrkeq7aQTfW4IsRiYeqP1nEXgmody8ah8t+Y3XqilzYdNiyR1kelEW9sJazA9Y D487Wit+CaoJ3/zxMbsAicVCW8vtAQuPPBgDQsHTI5FegVPVWxmoimiAvkRuNEbf tpvYS4KdeH0Vjx8YuWuk+VvSiA4uzF4jyA05rwVCNXP6zCFfLwBTtLJI+Ou8aBhi oSIz4gDvE1d/HtFeYq9kk9B05xYJA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudejgedgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepffdvffejueetleefieeludduuefgteejleevfeekjeefieegheet ffdvkeefgedunecuffhomhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrd dvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 9110F1080057; Mon, 7 Dec 2020 04:46:03 -0500 (EST) From: Thomas Monjalon To: Hideyuki Yamashita Cc: dev@dpdk.org, Ciara Power , bruce.richardson@intel.com, david.hunt@intel.com, "Ma, Liang" Date: Mon, 07 Dec 2020 10:46:02 +0100 Message-ID: <3140511.LMxrbLn5pV@thomas> In-Reply-To: <20201204075109.14694-1-yamashita.hideyuki@ntt-tx.co.jp> References: <20201204075109.14694-1-yamashita.hideyuki@ntt-tx.co.jp> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 0/5] add apistats function 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" 04/12/2020 08:51, Hideyuki Yamashita: > In general, DPDK application consumes CPU usage because it polls > incoming packets using rx_burst API in infinite loop. > This makes difficult to estimate how much CPU usage is really > used to send/receive packets by the DPDK application. > > For example, even if no incoming packets arriving, CPU usage > looks nearly 100% when observed by top command. > > It is beneficial if developers can observe real CPU usage of the > DPDK application. > Such information can be exported to monitoring application like > prometheus/graphana and shows CPU usage graphically. > > To achieve above, this patch set provides apistats functionality. > apistats provides the followiing two counters for each lcore. > - rx_burst_counts[RTE_MAX_LCORE] > - tx_burst_counts[RTE_MAX_LCORE] > Those accumulates rx_burst/tx_burst counts since the application starts. Please could you compare with what rte_jobstats offers? http://code.dpdk.org/dpdk/latest/source/lib/librte_jobstats/rte_jobstats.h I feel all of this shares the same goals as librte_power work. [...] > - basic API counting functionality(apistats) into librte_ethdev Could it be it be accessible via rte_telemetry? http://code.dpdk.org/dpdk/latest/source/lib/librte_telemetry/rte_telemetry.h