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 AD78641E7C;
Sun, 12 Mar 2023 09:40:35 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 5337A40F18;
Sun, 12 Mar 2023 09:40:35 +0100 (CET)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com
[64.147.123.20]) by mails.dpdk.org (Postfix) with ESMTP id 67FFD406A2
for <dev@dpdk.org>; Sun, 12 Mar 2023 09:40:33 +0100 (CET)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
by mailout.west.internal (Postfix) with ESMTP id F02FC32007BE;
Sun, 12 Mar 2023 04:40:31 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
by compute5.internal (MEProxy); Sun, 12 Mar 2023 04:40:32 -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=
1678610431; x=1678696831; bh=Fnbdbqf1kCLvrbdIZfvJRwIr5Pa77OcSBGt
C4jEJqPQ=; b=e49h7nKQJQbsO2qou8w5m4XVbXqb4fqnL8E8IE6CzEoVIJ+QeP9
jOtklpo3VzSVKL96pyMwpDIcbNiUuBEwHEUVJAEtnYWWyxIDozFim8xuioIm857A
/o8d+08M1GNQVp5BLumBno2WYXI7HZ/uTTmRJToa6xLcWh6P1yatfmLSm/5n7z7h
A2UvWk9xyUt22gSwgbF7/H0qqHFiIQ6f/sUpe5/57IGQPKX3cAKjFufa49w8kufl
7KVGCYGgCxa+JSms4c9vO1LzcMOKJrkRG6lBkcDgEZWIspHDvm3n77BoZdF0WmJU
Zx6x+Q3pcZJelrahjCIGVfXIAk7H3nCZDYw==
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=
1678610431; x=1678696831; bh=Fnbdbqf1kCLvrbdIZfvJRwIr5Pa77OcSBGt
C4jEJqPQ=; b=dlRcwbcWHxLhgqB89ZvRfliDnujx2dej8Sq/5JG7f9T3YGVu/Tg
ocRk5u22qowN4oYy5LDzAwtwI9ySZTLq43eBqF7IoCOtvsPy9CP+fh2z73b74xSp
piISj3Gzd9nxv+UfI0+WLYNiWCNf1Jz7qnily7ykJk5WBw2zdefpUlgNcUzXIMFm
8nuYB29n3/fFTm9YWS8YEuBuzkUGUvYjc42OqoU7DZ7dIN6lZVWFPySGiIFWm6YZ
+s3/v0YCTkuNAu17t70cLmCQMc/t6rvjjT85ArmKef64uUzgpXlYBkT2ii9f5xbC
3Bf4s8Rc00f3l/94dejISRpbpsgf3Z20uVw==
X-ME-Sender: <xms:_o8NZMz4NGLHicaoOmoQh-HuRMSZJhbPfrv8F0134-qV7BNDCyV0MQ>
<xme:_o8NZARTG_QK2LZVARm3nt8NBcyyh3MnFu7kINmDRlZpCgH6s5nDNDQXioH4sJ_RD
AqmmOhUd0AuOQPF6A>
X-ME-Received: <xmr:_o8NZOVISHPJg_aU_Sz18KK3En0_kAPWmNfGqpOLPCxqdJMUOVxQNweDMqkcNocsu3oU8e6TM98sJg1YV8oPeq1teA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddvuddguddvtdcutefuodetggdotefrod
ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh
necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd
enucfjughrpefhvfevufffkfgjfhgggfgtsehtqhertddttddunecuhfhrohhmpefvhhho
mhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqne
cuggftrfgrthhtvghrnhepfefhjeeluedvvedtuddtuedtvefhieejtefhffeujefhtedu
udevtdektdeikeffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh
hfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth
X-ME-Proxy: <xmx:_o8NZKgzRBVoKTqIYQVwFzxzan_d8yssMCn7uGUnw7yvg0agDEQ7ow>
<xmx:_o8NZOCylt-tkfpKkr11YJIpx8Q2V5g_wb07NIFpXUNnCjpu3hPAtA>
<xmx:_o8NZLIFRj8MSgh3bt_XdtzqqH2nGMWUeoSc-JltUSati3LynvfD8w>
<xmx:_48NZF7UXYJs39M7Oo1TCSuLJK8GNVxXqykW18t32st_Vq_irKcSfA>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun,
12 Mar 2023 04:40:29 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Huisong Li <lihuisong@huawei.com>, dev@dpdk.org
Cc: bruce.richardson@intel.com, hkalra@marvell.com, huangdaode@huawei.com,
fengchengwen@huawei.com,
Morten =?ISO-8859-1?Q?Br=F8rup?= <mb@smartsharesystems.com>
Subject: Re: [PATCH v2] mem: fix displaying heap ID failed for heap info
command
Date: Sun, 12 Mar 2023 09:40:28 +0100
Message-ID: <2181545.ZfL8zNpBrT@thomas>
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D87767@smartserver.smartshare.dk>
References: <20230209030341.9697-1-lihuisong@huawei.com>
<20230222074953.22715-1-lihuisong@huawei.com>
<98CBD80474FA8B44BF855DF32C47DC35D87767@smartserver.smartshare.dk>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
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
22/02/2023 08:53, Morten Br=F8rup:
> > From: Huisong Li [mailto:lihuisong@huawei.com]
> > Sent: Wednesday, 22 February 2023 08.50
> o command
> >=20
> > The telemetry lib has added a allowed characters set for dictionary nam=
es.
> > Please see commit 2537fb0c5f34 ("telemetry: limit characters allowed in
> > dictionary names")
> >=20
> > The space is not in this set, which cause the heap ID in /eal/heap_info
> > cannot be displayed. Additionally, 'heap' is also misspelling. So use
> > 'Heap_id' to replace 'Head id'.
> >=20
> > Fixes: e6732d0d6e26 ("mem: add telemetry infos")
> > Fixes: 2537fb0c5f34 ("telemetry: limit characters allowed in dictionary
> > names")
> > Cc: stable@dpdk.org
> >=20
> > Signed-off-by: Huisong Li <lihuisong@huawei.com>
> > Acked-by: Chengwen Feng <fengchengwen@huawei.com>
>=20
> Reviewed-by: Morten Br=F8rup <mb@smartsharesystems.com>
Applied, thanks.