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 BC47F41BE7; Mon, 6 Feb 2023 09:21:19 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9897942686; Mon, 6 Feb 2023 09:21:19 +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 77BD940FAE for <dev@dpdk.org>; Mon, 6 Feb 2023 09:21:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675671678; 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=j1CG9Fy8GUZrj/hS4M2MvSv7uGH+RECMv7Y2qZj3Xlc=; b=XWVi2+zL0XMV36g0560cnK7FC6z9cETj36n7ekXvCi0vhcK94q17HnOLe95/r/AasvgjYy h8s7yAAN0Q4Al42ZL1I58sacenwW4trEXmImppdInGKMwe9EThBnDShPM55AJ2EGKG058A fFruZVoT+EVApJuYIjjJr/Qpylaloiw= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-355-vmommfVROju_CJ7G-oyKsA-1; Mon, 06 Feb 2023 03:21:16 -0500 X-MC-Unique: vmommfVROju_CJ7G-oyKsA-1 Received: by mail-wm1-f71.google.com with SMTP id d18-20020a05600c34d200b003df901ab982so5392660wmq.4 for <dev@dpdk.org>; Mon, 06 Feb 2023 00:21:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:references:to:from:subject:cc:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=j1CG9Fy8GUZrj/hS4M2MvSv7uGH+RECMv7Y2qZj3Xlc=; b=seJptmwCY0I/W/P5xuatjA3vFaWm+u4bVgbNGwR6ikbXjTqiuhv5oeXvPJGgg7vXWc lgr1rGYzFzlR1NjQLwe+odVQoXbtZcpfZDKlEOlLOYhjsFjsLzty7+ZUQotbB42Lf6Iw O4pSs7RJze6WXQhIrhFnRNv0HWZ/4nYaxwYEakkhKdtj+1oUPVaoZIIblMS0CrJKAhKL qokwEYmigiJcZxWeQuXssa3uRQIAWJTgBaR552jo2gqeZnRvr+nTy2ox6fLzytpXkIty 3DaKS0FuybZ1yOaVT7d44dkulWUsVhHwoLuKwj6z4mgtiNUleuiCJYNmuMUqANALM+nW 0K8g== X-Gm-Message-State: AO0yUKXT1kwr/kzcPAnq1bFiu2d37OyERm6HDyoDgAKFddExo69flgj/ BDOSyABFLmw5nfj1H15x7p7KxQDgiAxM9dq+q7sRWMKU5svf7CcwF8fw7WBxnpXt4G9wa1evvZy 3Sm0= X-Received: by 2002:a05:600c:1e17:b0:3df:ed95:d757 with SMTP id ay23-20020a05600c1e1700b003dfed95d757mr9435530wmb.34.1675671675735; Mon, 06 Feb 2023 00:21:15 -0800 (PST) X-Google-Smtp-Source: AK7set8GY7tj3uUYgGQVWFY3r2fHtQ9FLD9YoR99mv0Ef34HsCv/FtQzs9Rr2C2lTQaGyhlR2xbMEQ== X-Received: by 2002:a05:600c:1e17:b0:3df:ed95:d757 with SMTP id ay23-20020a05600c1e1700b003dfed95d757mr9435522wmb.34.1675671675584; Mon, 06 Feb 2023 00:21:15 -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 k32-20020a05600c1ca000b003ddf2865aeasm16493459wms.41.2023.02.06.00.21.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Feb 2023 00:21:15 -0800 (PST) Mime-Version: 1.0 Date: Mon, 06 Feb 2023 09:21:14 +0100 Message-Id: <CQBC187TOCWX.3OLVWIMGYB6PR@ringo> Cc: "Kevin Laatz" <kevin.laatz@intel.com> Subject: Re: [PATCH v8 2/5] eal: report applications lcore usage From: "Robin Jarry" <rjarry@redhat.com> To: =?utf-8?q?Morten_Br=C3=B8rup?= <mb@smartsharesystems.com>, "fengchengwen" <fengchengwen@huawei.com>, <dev@dpdk.org> X-Mailer: aerc/0.14.0-60-gc1f7df1a0e5f-dirty References: <20221123102612.1688865-1-rjarry@redhat.com> <20230202134329.539625-1-rjarry@redhat.com> <20230202134329.539625-3-rjarry@redhat.com> <134bf55e-ff9b-4ab0-bb16-3347f7b3c95f@huawei.com> <98CBD80474FA8B44BF855DF32C47DC35D876FF@smartserver.smartshare.dk> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D876FF@smartserver.smartshare.dk> X-Mimecast-Spam-Score: 1 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8; format=Flowed 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 Morten Br=C3=B8rup, Feb 06, 2023 at 08:36: > > The 'record_burst_stats' also important for performance tune. > > While I agree that burst size spread is important for comparing CPU=20 > usage and capacity, the 'record_burst_stats' is a test_pmd specific=20 > feature. Applications may implement something different. > > > Is it possible to incorporate it into this framework? > > We all agreed on CPU usage metrics for this patch, so let's limit=20 > ourselves this time. > > If we want more performance metrics, such as RX and TX burst size=20 > spread, they can be proposed and discussed in a separate RFC. It might=20 > trigger a lot of discussion, like the original lcore busyness patch=20 > that inspired this patch series. I agree with Morten here. This framework should only allow reporting=20 statistics that are not specific to any DPDK application.