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 2639D4240B; Wed, 18 Jan 2023 10:13:08 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BA4D140223; Wed, 18 Jan 2023 10:13:07 +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 097014003F for ; Wed, 18 Jan 2023 10:13:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674033185; 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=JbgeNi12fTO/6Kd24inhqGVe1F1Y1w06YyPqz/JEj/0=; b=AqgTzrSRAckqNL4ykKiPhFEtpu0UIvYuZlUMEm2CHjfxERomstdh/fnqF2oe2Hr67TDLYW eMiWShMin9D1wu5RBupBni31mD14jpGa7nIiJFJRtLjLyBaHXB2qjH2GD65TXr6Tuo4Upr FhPlQoqosD1/JjxwuexnrYVHG93utoM= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-477-UAIdHvdOM4yTXwKvNs1ogw-1; Wed, 18 Jan 2023 04:13:04 -0500 X-MC-Unique: UAIdHvdOM4yTXwKvNs1ogw-1 Received: by mail-wm1-f69.google.com with SMTP id c66-20020a1c3545000000b003d355c13229so927191wma.0 for ; Wed, 18 Jan 2023 01:13:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:references:message-id:to:from:subject:cc:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=JbgeNi12fTO/6Kd24inhqGVe1F1Y1w06YyPqz/JEj/0=; b=toVXc3ttX+PO1MqDVvFK4wrZCnzBiArNWaqOXzxdGH7ebTowbSOI0X2wZrCJrPeEoD kFwlH66bZqynLlZEsQClupJJupysUMyartwVbZYxRHNl2lKhM24Pv3JwS1vllfMsuTgw bqaofez1AQ0xLJEcimURAF8+gpiboo5uh6pwGbtEzAUI7LigoHlnTKTxnnP3jf28qzTz 9tX39WCgmHR5lwByFgq3YLLoImS4uHiykKzSO8aAWfDk+GolYyeL8OdzHR3+RuSK7ISg z+HQ4AG07q71IrFUvwT02aJv9YaBC3Cxqkn2hrCjZZR+d9ziChgeedd54s+cy9HB6QLQ t+tA== X-Gm-Message-State: AFqh2koHJCrT3f47DjMkMRsx2X7UfbaR5Bs/URqgW+0WSXm73BKI1CJt 4PJ0G+rAX2DNBBFwIUdZr2ybE4ZFAN3IZMBnj9Zuj7cLwrg1jcygpz8/NTLjgzOdTClHCa8Aaph /jjLw2+jYo5IUyA4B9Wf9vQD6YwbJ7phsygUCUTd0tSmMwkx2mLJG X-Received: by 2002:a5d:6b01:0:b0:2bd:fd81:b503 with SMTP id v1-20020a5d6b01000000b002bdfd81b503mr5643408wrw.1.1674033183166; Wed, 18 Jan 2023 01:13:03 -0800 (PST) X-Google-Smtp-Source: AMrXdXuNoKRm7PswbBCFglLDmRI5pqgaD0FBta37obiuoFqSx4DUSK4jVKosLinlI26L/qlKF62u6Q== X-Received: by 2002:a5d:6b01:0:b0:2bd:fd81:b503 with SMTP id v1-20020a5d6b01000000b002bdfd81b503mr5643389wrw.1.1674033182931; Wed, 18 Jan 2023 01:13:02 -0800 (PST) Received: from localhost (2a01cb000f483e0055ae3800781b5cbc.ipv6.abo.wanadoo.fr. [2a01:cb00:f48:3e00:55ae:3800:781b:5cbc]) by smtp.gmail.com with ESMTPSA id j14-20020adff00e000000b0024cb961b6aesm30165849wro.104.2023.01.18.01.13.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 18 Jan 2023 01:13:02 -0800 (PST) Mime-Version: 1.0 Date: Wed, 18 Jan 2023 10:13:02 +0100 Cc: "Tyler Retzlaff" , "Kevin Laatz" , "Konstantin Ananyev" , =?utf-8?q?Mattias_R=C3=B6nnblom?= Subject: Re: [PATCH v5 0/4] lcore telemetry improvements From: "Robin Jarry" To: , "Thomas Monjalon" , "David Marchand" Message-Id: X-Mailer: aerc/0.14.0-31-g01280214150a-dirty References: <20221123102612.1688865-1-rjarry@redhat.com> <20221216102109.64142-1-rjarry@redhat.com> In-Reply-To: <20221216102109.64142-1-rjarry@redhat.com> X-Mimecast-Spam-Score: 1 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 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 Robin Jarry, Dec 16, 2022 at 11:21: > This is a follow up on previous work by Kevin Laatz: > > http://patches.dpdk.org/project/dpdk/list/?series=3D24658&state=3D* > > 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/643e672fe388e348ea7ccbbda6f5a87a066f= d919 Since there was no negative feedback, can this be applied for -rc1 once I fixed the reported cosmetic issues? Thanks.