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 50DFB41C33; Tue, 7 Feb 2023 20:37:43 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D69184021F; Tue, 7 Feb 2023 20:37:42 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 690C340151 for ; Tue, 7 Feb 2023 20:37:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675798660; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lF2E+UFgt7lMFr9FJ3/sjFDigKgyEIj7iPj1ArAPcas=; b=QpBc2cqceMpPTasx6BMsxUWs1PLlhtFjWi8hhlBB8YD/lG/kq0pHy0JB7kojzBUftKILwm pL0+7hk3mI8Ii/omm7ZVwgkx+P29qc44r28kn7Lk2CqpbncPjziTie2lv1H4RQCqxeTkaJ vfyVYj55jeo3m1z7mhsNDj7NZme2A9A= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-433-ItAkx6mpNca0IWs7wnZINA-1; Tue, 07 Feb 2023 14:37:39 -0500 X-MC-Unique: ItAkx6mpNca0IWs7wnZINA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5A4423C18349 for ; Tue, 7 Feb 2023 19:37:39 +0000 (UTC) Received: from ringo.home (unknown [10.39.208.16]) by smtp.corp.redhat.com (Postfix) with ESMTP id AF7321121314; Tue, 7 Feb 2023 19:37:38 +0000 (UTC) From: Robin Jarry To: dev@dpdk.org Cc: Robin Jarry Subject: [PATCH v9 0/5] lcore telemetry improvements Date: Tue, 7 Feb 2023 20:37:26 +0100 Message-Id: <20230207193731.1242505-1-rjarry@redhat.com> In-Reply-To: <20221123102612.1688865-1-rjarry@redhat.com> References: <20221123102612.1688865-1-rjarry@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 This is a follow up on previous work by Kevin Laatz: http://patches.dpdk.org/project/dpdk/list/?series=24658&state=* This series is aimed at allowing DPDK applications to expose their CPU usage stats in the DPDK telemetry under /eal/lcore/info. This is a much more basic and naive approach which leaves the cpu cycles accounting completely up to the application. For reference, I have implemented a draft patch in OvS to use rte_lcore_register_usage_cb() and report the already available busy cycles information. https://github.com/rjarry/ovs/commit/643e672fe388e348ea7ccbbda6f5a87a066fd919 v9: - Fixed changelog & version.map order. - Updated with 64-bit integer telemetry functions. - Refined docstrings (added notice about resetting the callback). - Fixed accounting of total cycles in testpmd. v8: - Made /eal/lcore/info lcore_id argument parsing more robust. Robin Jarry (5): eal: add lcore info in telemetry eal: report applications lcore usage app/testpmd: add dump command for lcores app/testpmd: report lcore usage eal: add lcore usage telemetry endpoint app/test-pmd/cmdline.c | 3 + app/test-pmd/noisy_vnf.c | 7 +- app/test-pmd/testpmd.c | 42 +++- app/test-pmd/testpmd.h | 25 ++- app/test-pmd/txonly.c | 2 +- doc/guides/rel_notes/release_23_03.rst | 8 + doc/guides/testpmd_app_ug/testpmd_funcs.rst | 7 + lib/eal/common/eal_common_lcore.c | 219 ++++++++++++++++++-- lib/eal/include/rte_lcore.h | 48 +++++ lib/eal/version.map | 1 + 10 files changed, 329 insertions(+), 33 deletions(-) -- 2.39.1