DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: fengchengwen <fengchengwen@huawei.com>
Cc: Huisong Li <lihuisong@huawei.com>,
	dev@dpdk.org, bruce.richardson@intel.com,
	mb@smartsharesystems.com, huangdaode@huawei.com,
	liudongdong3@huawei.com
Subject: Re: [PATCH] mem: fix displaying heap ID failed for heap info command
Date: Thu, 9 Feb 2023 09:48:54 +0100	[thread overview]
Message-ID: <CAJFAV8wmTZ5gHLFzRU18d7NiRHF46puC8k7PRBAMP8WgFUcz2A@mail.gmail.com> (raw)
In-Reply-To: <a61aedbc-fa2a-0dea-0852-770256242f00@huawei.com>

On Thu, Feb 9, 2023 at 4:24 AM fengchengwen <fengchengwen@huawei.com> wrote:
>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
>
> And, how abort add error log in telemetry valid_name, so so that problems can
> be identified as early as possible.
>
> On 2023/2/9 11:03, Huisong Li wrote:
> > The telemetry lib has added a allowed characters set for dictionary names,
> > See commit
> > 2537fb0c5f34 ("telemetry: limit characters allowed in dictionary names")
> >
> > 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

I agree this typo is ugly, but I wonder if some telemetry users
started relying on it...


> > 'Heap_id' to replace 'Head id'.
> >
> > Fixes: e6732d0d6e26 ("mem: add telemetry infos")

IIUC, the commit that broke displaying "Head id" is actually the one
that limited the set of chars.


> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Huisong Li <lihuisong@huawei.com>


-- 
David Marchand


  reply	other threads:[~2023-02-09  8:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09  3:03 Huisong Li
2023-02-09  3:23 ` fengchengwen
2023-02-09  8:48   ` David Marchand [this message]
2023-02-11  2:58     ` lihuisong (C)
2023-02-11  3:04   ` lihuisong (C)
2023-02-22  7:49 ` [PATCH v2] " Huisong Li
2023-02-22  7:53   ` Morten Brørup
2023-03-12  8:40     ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJFAV8wmTZ5gHLFzRU18d7NiRHF46puC8k7PRBAMP8WgFUcz2A@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=huangdaode@huawei.com \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=mb@smartsharesystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).