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 4343941BE3; Mon, 6 Feb 2023 00:30:39 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DC47240ED7; Mon, 6 Feb 2023 00:30:38 +0100 (CET) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 423E840A7D for ; Mon, 6 Feb 2023 00:30:38 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D878E5C0136; Sun, 5 Feb 2023 18:30:36 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 05 Feb 2023 18:30:36 -0500 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=1675639836; x= 1675726236; bh=WeA4OmqMJdhauTs03KXV2K4Jf5zfdE5UiUCO8VaomCQ=; b=Q rXSTskn69J2PfdJCrAYwuSW/kZ58CutL/ZpaJzKF4ypQt0kGYTbRZhFsnLyqW8U2 ZjUenXDNa3GcN59fubCWGeEeIldM2N+Ec93QTBpIOFW/0t4Cr21JdmvnJL/AXJKL KHgag6y+3baacUigJKXKCDVk+zLwMYZpRcfrH03vOirpC27bga/TRnMq3l7Tue7o iysmDGjreSiWVBn6JmYFUH8hLely71Ezv1h6oRg9Wnva2vu4efeeDgoy6vuw+VBd adlUE7jDRkMh18seWfWkGZLtfJkwfaUPqIb8aQuXP3F8OCr621ut17StupoPAKI6 n3ItseCQGRsF8dmaBzQiw== 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=1675639836; x= 1675726236; bh=WeA4OmqMJdhauTs03KXV2K4Jf5zfdE5UiUCO8VaomCQ=; b=c NIjYYCy6s7yPTn9ruHZxKO7NshfxQVApmuynaxy17IxAWZ6HrLfoqYVruo6QADet a5P/RjwLM9Kkz67fhPeZYI7ASIGgPYdKHer2luxOM3mnQoXXGWAyu32AfcoLKiuo xsEjlhMKg3/bu76NgjCjCy/8gnCgNOldb/9knmjHIctdQFTnNcMpNcWL3hCN+WR/ TlvjCsB8+jiR+uuUsOhCWJ20j8j5+2tK+S8L0AAIIVSuXoHIfAF3X5aPoFxU0Qs3 dYijfR+CuhY0lAj2Lb2Ca42+T0cvs5s+mhN1XsEstg9XkqOLc0G1A+5mHPxiQ0Or TY+075NzLim9jN6w8w2wQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeghedgtdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtudenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeefhfejleeuvdevtddutdeutdevhfeijeethfffueejhfetuddu vedtkedtieekffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 5 Feb 2023 18:30:35 -0500 (EST) From: Thomas Monjalon To: Robin Jarry Cc: dev@dpdk.org, olivier.matz@6wind.com, andrew.rybchenko@oktetlabs.ru, Morten =?ISO-8859-1?Q?Br=F8rup?= Subject: Re: [PATCH] mempool: add object usage counts for the telemetry api Date: Mon, 06 Feb 2023 00:30:34 +0100 Message-ID: <2620111.X9hSmTKtgW@thomas> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D874BE@smartserver.smartshare.dk> References: <20221115153555.947526-1-rjarry@redhat.com> <98CBD80474FA8B44BF855DF32C47DC35D874BE@smartserver.smartshare.dk> 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 15/11/2022 17:28, Morten Br=F8rup: > +CC mempool maintainers >=20 > > From: Robin Jarry [mailto:rjarry@redhat.com] > > Sent: Tuesday, 15 November 2022 16.36 > >=20 > > rte_mempool_dump() already returns the number of objects available and > > in the cache. This information is missing from the telemetry API. Add > > it > > albeit with less granularity for cached counts (only report the > > total_cache_count). > >=20 > > Signed-off-by: Robin Jarry > > --- >=20 > Please consider that the individual per-lcore cache lengths could be info= rmative for some applications too. >=20 > Anyway, they could be provided in a later patch. >=20 > Acked-by: Morten Br=F8rup Rebased and applied, thanks.