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 720EB41C4D; Thu, 9 Feb 2023 10:45:28 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DF39042B8E; Thu, 9 Feb 2023 10:44:08 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 82911400D5 for ; Thu, 9 Feb 2023 10:44:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675935847; 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=QDoKLm/cVvILvqZfKRbt0NiSefBp4zZ5XjF2jgDnPO8=; b=SxPenyhA+l6tDU5AXw9pwBQjznTMh5vc7tCdEl6bs1fzweqI7bxHtOFvUfKo4NWxnaFFa6 65ByKZvNL7jb/h/7t003I+eA7oVf4XNpeE96jbneL4NVh+R5XmwpsPpehRGhTqQjjK12kx NnBjLXXXU3BWlD9BODfgrFpl1SeHhao= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-248-D0Y85SgWOkuU10s2HrBkrg-1; Thu, 09 Feb 2023 04:44:05 -0500 X-MC-Unique: D0Y85SgWOkuU10s2HrBkrg-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 92151811E6E for ; Thu, 9 Feb 2023 09:44:05 +0000 (UTC) Received: from ringo.redhat.com (unknown [10.39.208.33]) by smtp.corp.redhat.com (Postfix) with ESMTP id EC42AC16023; Thu, 9 Feb 2023 09:44:04 +0000 (UTC) From: Robin Jarry To: dev@dpdk.org Cc: Robin Jarry Subject: [PATCH v10 0/5] lcore telemetry improvements Date: Thu, 9 Feb 2023 10:43:49 +0100 Message-Id: <20230209094354.1377424-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.8 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 v10: - Code style fix - Fixed reset of total_cycles while lcore is running 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. 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 | 8 +- app/test-pmd/testpmd.c | 44 +++- app/test-pmd/testpmd.h | 25 ++- 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 | 222 ++++++++++++++++++-- lib/eal/include/rte_lcore.h | 48 +++++ lib/eal/version.map | 1 + 9 files changed, 335 insertions(+), 31 deletions(-) -- 2.39.1