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 BD9AFA0032;
	Mon, 18 Jul 2022 17:46:59 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id A1A8540698;
	Mon, 18 Jul 2022 17:46:59 +0200 (CEST)
Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com
 [209.85.214.176])
 by mails.dpdk.org (Postfix) with ESMTP id 64DD440041
 for <dev@dpdk.org>; Mon, 18 Jul 2022 17:46:58 +0200 (CEST)
Received: by mail-pl1-f176.google.com with SMTP id 5so9377318plk.9
 for <dev@dpdk.org>; Mon, 18 Jul 2022 08:46:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=networkplumber-org.20210112.gappssmtp.com; s=20210112;
 h=date:from:to:cc:subject:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding;
 bh=EOZii+Ucc6hKY/ZRTAt+Hwhc9YBRrnwcSpQC1iGU9/k=;
 b=PTbq+qlKV5U8gkCL68qXkSDxjZgc6mTQYGsulE1d0i3slHh9b2iuTRKFV1LYXwYXKF
 PJqs2WdVSWuQ6jrW5PuMffyLdAKfY9e3n0hFO6Im16F78Ci7C24SWOIXDyjgeZEyJ9Jv
 TgaLIrL5tg+gPZTmcSMqvPUUldXoMHwz6KXbPfrscvgU1JWMs8GSJwBlSreW08MfYIQ5
 ispRbWNjLfWgr7XyubNY1iIYou2syecw/fYI3s0NnboIfNRTok4UghO814sm+XX+DzGp
 zGa/P6QrBe6Kq7SpnK6zICBykLXUX/A86YX8mrwGhQrQtJxYsc244uhnMwzmUpK3kF0X
 1s2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-transfer-encoding;
 bh=EOZii+Ucc6hKY/ZRTAt+Hwhc9YBRrnwcSpQC1iGU9/k=;
 b=zMSms+CUiE1FOZEv3CSdac5iGKj0h+YRagNdxebjhkF5CW4qZQId4/TW6J0VLDDjW+
 hfPCKtFc8qvAoAuqkW+cExUQB+RSgu5rzEGzJoallWNB0+JRGqklLq3rxBZ5kDjNhMcn
 eKvFKvolaC4lZ5vCYXz85z1JMXBtSr1JyJ263Jyafdvca6QtqFxXERdZsgJpQBZpp9F+
 psKO/viHKUBhyl1ljpKF5WDQs40sisSiRXuneMsvwoTv4YHp6yvuMU63tBMBXykvnSvJ
 Z2XEUXoQ4enhTPieLkpp2a/3FBcXOFjWaHsTc6rvhDBqVquUuxXXx5S9L3xOZ3rdtfwz
 6I4w==
X-Gm-Message-State: AJIora845ZTUJrW7eisciPAOFN0UagcZl/rV+EXqRIkwElV/ItThIvV1
 w7x90NX+6dmeNtzw/P1QpPGFGQ==
X-Google-Smtp-Source: AGRyM1vD+KVRhGKaHr4MR6wnFcIoev6JOytsFrhNoFSFGnisp/8Zo35SYsv6FD7/a4Lmai/3n6NSWQ==
X-Received: by 2002:a17:90b:4a4d:b0:1ef:bc34:405a with SMTP id
 lb13-20020a17090b4a4d00b001efbc34405amr32392654pjb.96.1658159217340; 
 Mon, 18 Jul 2022 08:46:57 -0700 (PDT)
Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218])
 by smtp.gmail.com with ESMTPSA id
 w29-20020a63491d000000b003fadd680908sm8327533pga.83.2022.07.18.08.46.56
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Mon, 18 Jul 2022 08:46:56 -0700 (PDT)
Date: Mon, 18 Jul 2022 08:46:53 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Morten =?UTF-8?B?QnLDuHJ1cA==?= <mb@smartsharesystems.com>, "Honnappa
 Nagarahalli" <Honnappa.Nagarahalli@arm.com>, <dev@dpdk.org>, Bruce
 Richardson <bruce.richardson@intel.com>, Nicolas Chautru
 <nicolas.chautru@intel.com>, Fan Zhang <roy.fan.zhang@intel.com>, Ashish
 Gupta <ashish.gupta@marvell.com>, Akhil Goyal <gakhil@marvell.com>, David
 Hunt <david.hunt@intel.com>, "Chengwen Feng" <fengchengwen@huawei.com>,
 Kevin Laatz <kevin.laatz@intel.com>, "Ray Kinsella" <mdr@ashroe.eu>,
 <thomas@monjalon.net>, Ferruh Yigit <ferruh.yigit@xilinx.com>, Andrew
 Rybchenko <andrew.rybchenko@oktetlabs.ru>, <jerinj@marvell.com>, Sachin
 Saxena <sachin.saxena@oss.nxp.com>, <hemant.agrawal@nxp.com>, Ori Kam
 <orika@nvidia.com>, Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
 Conor Walsh <conor.walsh@intel.com>, nd <nd@arm.com>
Subject: Re: [PATCH v1 1/2] eal: add lcore busyness telemetry
Message-ID: <20220718084653.3e3b1a31@hermes.local>
In-Reply-To: <9a27efbd-31d1-7525-51b0-ead0d969e98a@intel.com>
References: <24c49429394294cfbf0d9c506b205029bac77c8b.1657890378.git.anatoly.burakov@intel.com>
 <98CBD80474FA8B44BF855DF32C47DC35D871CC@smartserver.smartshare.dk>
 <DBAPR08MB5814A83A1E834AABF81296D2988D9@DBAPR08MB5814.eurprd08.prod.outlook.com>
 <98CBD80474FA8B44BF855DF32C47DC35D871CD@smartserver.smartshare.dk>
 <9a27efbd-31d1-7525-51b0-ead0d969e98a@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 Mon, 18 Jul 2022 10:43:52 +0100
"Burakov, Anatoly" <anatoly.burakov@intel.com> wrote:

> >>> This is an "alternative fact"! Only run-to-completion applications  
> >> polls for RX.  
> >>> Pipelined applications do not poll for packets in every pipeline  
> >> stage.
> >> I guess you meant, poll for packets from NIC. They still need to
> >> receive packets from queues. We could do a similar thing for rte_ring
> >> APIs.  
> 
> Ring API is already instrumented to report telemetry in the same way, so 
> any rte_ring-based pipeline will be able to track it. Obviously, 
> non-DPDK API's will have to be instrumented too, we really can't do 
> anything about that from inside DPDK.

The eventdev API is used to build pipeline based app's and it supports
telemetry.