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 0333042D09;
Tue, 20 Jun 2023 16:35:03 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id DB2FD410D7;
Tue, 20 Jun 2023 16:35:03 +0200 (CEST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
[66.111.4.29]) by mails.dpdk.org (Postfix) with ESMTP id 49D0D4068E
for <dev@dpdk.org>; Tue, 20 Jun 2023 16:35:03 +0200 (CEST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47])
by mailout.nyi.internal (Postfix) with ESMTP id C7EAA5C02B3;
Tue, 20 Jun 2023 10:35:02 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
by compute6.internal (MEProxy); Tue, 20 Jun 2023 10:35:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
cc:cc:content-transfer-encoding:content-type:content-type:date
:date:from:from:in-reply-to:in-reply-to:message-id:mime-version
:references:reply-to:sender:subject:subject:to:to; s=fm2; t=
1687271702; x=1687358102; bh=NEkEMTVa6piRevuRSgcm3Nol3Bbz7BG3R+x
qBlWQMlw=; b=m76beuC1LoAeX8b97b0bTwTGDlj7KpJAR/sFIm0T/4EHM15gxoA
vBNK18u8P+Rxc1MH/FCiOffU3NmvXbI+Zlr3uo0v1dkyVkLbTO/nmy+2aZI7Wj11
tslS/90R77i8ei/ZIo8pFLcUKQuOlKfJo4VMP4GVituyWRjoZIr173n4SQDySStV
I+ivCS0+5QEd+sTvHQ4XikngvDeiKTWfbaaqHPY304WONDW771IDVFLE77CDohk5
m2mCAZpGirYBB4EeRq6PvMAVy+10KKQuLM35bsxhawYKMWzAOlTcDEeouehQX8IZ
QBpaIWFR7Q223QggUx2i9HqfJ+aowGKF7Rg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=cc:cc:content-transfer-encoding
:content-type:content-type:date:date:feedback-id:feedback-id
:from:from:in-reply-to:in-reply-to:message-id:mime-version
:references:reply-to:sender:subject:subject:to:to:x-me-proxy
:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=
1687271702; x=1687358102; bh=NEkEMTVa6piRevuRSgcm3Nol3Bbz7BG3R+x
qBlWQMlw=; b=FbgDct10kw+f05fSB6lAwH23sWoJjGItY0zzhnxUx+pYPka5rz8
grJckxFJtAgFGV8qB410DL5dvn7EKtVEu3OUKHy33oSaifUT+ag2E1uAIPDHeueY
76JS0x73a5UEnv7LEcnAI2CpxfTjtd8GzdFLYYOeEjpzIad1QyeZumBPrhJ8c25F
+rvMAoA5HG/ajjegcl+ApmrnYWUaA4Bqxg+hjB7Prl5ZqC8AOP1IqI3RS+TtWB+e
Z3ASOVull8F8+UN3l7MsqbDZ/HXzC5XIkA4f16Z9WEuWWCrn4wiFPquAe2E+SYZx
GmC5v94loIOrTfVmqTkCEQ1lPxIsclV/B+Q==
X-ME-Sender: <xms:FrmRZOKOPwv6_eTi_QW9hQX1Br8AT6p4rrZ98TrpvdFiyRTy_Gc0FQ>
<xme:FrmRZGL-vOBjLeLL_KH_ala0pSnamq4lebReR7nD6C1ZlPUwczCXRU8Zm6LfLbYCK
d2BHYTtvecnj_vkpg>
X-ME-Received: <xmr:FrmRZOuzvPJounjtPUj6wmNytwdmyooqEJXtjTfjYbV2EC69af2baa45mvh6BHC0-rAmf2tT2WqyPyeiIMVN8RkDCg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgeefhedgheeiucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm
rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc
ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei
kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh
hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght
X-ME-Proxy: <xmx:FrmRZDYphc8B_lLuTjqIqw87tVrxTgmXj_jX0lcGxUB9ASMdUN7BeA>
<xmx:FrmRZFbUxAzncfkOWGsL1c2l7iSMwLV4At4WaotjasBWs8HOF1bdng>
<xmx:FrmRZPBIwhqiWp7sNeiB4Px2vTlnvUn6lu39adPKCC8dH2KeIpdMig>
<xmx:FrmRZIw0YLdVpI_BzKah0ZxRsfyU0vuPrU7PKRdVy1_majGg_Heiig>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue,
20 Jun 2023 10:35:01 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>, Jie Hai <haijie1@huawei.com>
Cc: honnappa.nagarahalli@arm.com, konstantin.v.ananyev@yandex.ru,
dev@dpdk.org, liudongdong3@huawei.com, bruce.richardson@intel.com
Subject: Re: [PATCH v4 3/3] ring: add telemetry cmd for ring info
Date: Tue, 20 Jun 2023 16:34:59 +0200
Message-ID: <4273274.ejJDZkT8p0@thomas>
In-Reply-To: <e71aef71-f34a-4c5a-e564-97c63a4c5239@huawei.com>
References: <20230131022841.10775-1-haijie1@huawei.com>
<CAJFAV8xv90rTGG+ePr+M_M80vx8xSs9c-vJU7UpyE0jyXKXDYg@mail.gmail.com>
<e71aef71-f34a-4c5a-e564-97c63a4c5239@huawei.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
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
20/06/2023 10:14, Jie Hai:
> On 2023/2/20 20:55, David Marchand wrote:
> > On Fri, Feb 10, 2023 at 3:50 AM Jie Hai <haijie1@huawei.com> wrote:
> >>
> >> This patch supports dump of ring information by its name.
> >> An example using this command is shown below:
> >>
> >> --> /ring/info,MP_mb_pool_0
> >> {
> >> "/ring/info": {
> >> "name": "MP_mb_pool_0",
> >> "socket": 0,
> >> "flags": "0x0",
> >> "producer_type": "MP",
> >> "consumer_type": "MC",
> >> "size": 262144,
> >> "mask": "0x3ffff",
> >> "capacity": 262143,
> >> "used_count": 153197,
> >> "consumer_tail": 2259,
> >> "consumer_head": 2259,
> >> "producer_tail": 155456,
> >> "producer_head": 155456,
> >
> > What would an external user make of such an information?
> >
> > I'd like to have a better idea what your usecase is.
> > If it is for debugging, well, gdb is probably a better candidate.
> >
> >
> Hi David,
> Thanks for your question and I'm sorry for getting back to you so late.
> There was a problem with my mailbox and I lost all my mails.
>
> The ring information exported by telemetry can be used to check the ring
> status periodically during normal use. When an error occurs, the fault
> cause can be deduced based on the information.
> GDB is more suitable for locating errors only when they are sure that
> errors will occur.
Yes, when an error occurs, you can use GDB,
and you don't need all these internal values in telemetry.