From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 61090A00C5; Wed, 14 Sep 2022 16:34:02 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EE6764021D; Wed, 14 Sep 2022 16:34:01 +0200 (CEST) Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by mails.dpdk.org (Postfix) with ESMTP id 6621540156 for <dev@dpdk.org>; Wed, 14 Sep 2022 16:34:01 +0200 (CEST) Received: by mail-pg1-f182.google.com with SMTP id h188so14471769pgc.12 for <dev@dpdk.org>; Wed, 14 Sep 2022 07:34:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date; bh=qhrSame5MVUn9cjG0LHqEdYgA73Rp1TWgNKbM/u3fnM=; b=6ZtFm+DVSyEdUCuImYqlyjzVuMNRSdfWNEAeGUvuVxSEWXvtQd0T10WyvyybC6pPJA aWk7mLum8w9CNrwVk7tagMyIp2AIuSwanWbztRMbiwnUmXHbZYwePF04dLjXPxf5XbqV FHf81dABHY+MtPGAWD7qVNoQIPwDFvHKkUraCLmFydLEKEP3L7MSD5IDAvujANmmKSGM PuWYbn4vBFvYrvk5FCJqHfGKPRjs5rIKV7aklmLk7h69QY+Jx0oHvXWkfGWbEdZXPj4z dClPM/R9VH1aTiGc0N5lxMuuo6U4kdqEWDeib+sQH1ogZh5JKPFcJLpgArmvRKY2anuj +nSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date; bh=qhrSame5MVUn9cjG0LHqEdYgA73Rp1TWgNKbM/u3fnM=; b=ZCNuisU/jkeoIrh1Gqz+W95jQ7I6pnBpA39LlolCftzyW6pAWVOcB6NYyivO/z0zgS 6VWhElQdS+K/pfM8P9zgw8QBHb4N2pO6lgjStTssp6OndHrUik6gBVowAGwaKupdCClG jHNtf3eruMrRwbO4K7hDXwPz3FTqTIxBkk3W7x5YKSuuP4wffxNqB+rqsU6BoRKKJIYX FtN/AmtaHXnkgEKk3b/t4qfYBZKZbPymv4WUIZ3mBVP6cCnaxmL3NNdoDbEYFT1garln 5LTtqDY3+LY5ialWNHXsGn+gLXyUx7mfBa8lPt11dawZiudH8LV0zfaZpYlj8Xpx+m7D Gcqw== X-Gm-Message-State: ACgBeo3VE+Una3DfbYBwwnkVE471ifxqcW27d4rb1AEWAJiPqe3yK6aL Msw6/yQF8e0YSBLwBiKhAjMkyA== X-Google-Smtp-Source: AA6agR6Ns66fgu5E2kaGx5M4VHzZ6FMrBQAjiZxsO8jFXtzYhjabF/O0GGmMO+GFy3gDLemycdHYoQ== X-Received: by 2002:a65:6753:0:b0:438:e83a:bebc with SMTP id c19-20020a656753000000b00438e83abebcmr14023877pgu.602.1663166040544; Wed, 14 Sep 2022 07:34:00 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id p129-20020a625b87000000b0053e0d6f353esm10197329pfb.27.2022.09.14.07.34.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Sep 2022 07:34:00 -0700 (PDT) Date: Wed, 14 Sep 2022 07:33:59 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: Kevin Laatz <kevin.laatz@intel.com> Cc: dev@dpdk.org, anatoly.burakov@intel.com Subject: Re: [PATCH v7 0/4] Add lcore poll busyness telemetry Message-ID: <20220914073359.6c57fbed@hermes.local> In-Reply-To: <20220914092929.1159773-1-kevin.laatz@intel.com> References: <24c49429394294cfbf0d9c506b205029bac77c8b.1657890378.git.anatoly.burakov@intel.com> <20220914092929.1159773-1-kevin.laatz@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org On Wed, 14 Sep 2022 10:29:25 +0100 Kevin Laatz <kevin.laatz@intel.com> wrote: > Currently, there is no way to measure lcore polling busyness in a passive > way, without any modifications to the application. This patchset adds a new > EAL API that will be able to passively track core polling busyness. As part > of the set, new telemetry endpoints are added to read the generate metrics. How much does measuring busyness impact performance?? In the past, calling rte_rdsc() would slow down packet rate because it is stops CPU pipeline. Maybe better on more modern processors, haven't measured it lately.