From: Stephen Hemminger <stephen@networkplumber.org>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: "Kevin Laatz" <kevin.laatz@intel.com>,
"Robin Jarry" <rjarry@redhat.com>,
"Morten Brørup" <mb@smartsharesystems.com>,
dev@dpdk.org, honnappa.nagarahalli@arm.com, nd@arm.com,
stable@dpdk.org
Subject: Re: [PATCH] eal: stop iteration after lcore info is processed
Date: Wed, 1 Nov 2023 11:13:39 -0700 [thread overview]
Message-ID: <20231101111339.27ecfcd6@fedora> (raw)
In-Reply-To: <20231101072053.1319697-1-ruifeng.wang@arm.com>
On Wed, 1 Nov 2023 15:20:53 +0800
Ruifeng Wang <ruifeng.wang@arm.com> wrote:
> From: Ruifeng Wang <ruifeng.wang@arm.com>
> To: Kevin Laatz <kevin.laatz@intel.com>, Robin Jarry <rjarry@redhat.com>, Morten Brørup <mb@smartsharesystems.com>
> Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, nd@arm.com, Ruifeng Wang <ruifeng.wang@arm.com>, stable@dpdk.org
> Subject: [PATCH] eal: stop iteration after lcore info is processed
> Date: Wed, 1 Nov 2023 15:20:53 +0800
> X-Mailer: git-send-email 2.25.1
>
> Telemetry iterates on lcore ID to collect info of a specific lcore.
> Since only one lcore is processed at a time, the iteration can stop
> when a matching lcore is found.
>
> Fixes: f2b852d909f9 ("eal: add lcore info in telemetry")
> Cc: rjarry@redhat.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
Looks like a good optimization. Not sure it needs to go to stable.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2023-11-01 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 7:20 [PATCH] eal: stop iteration after lcore info is processed Ruifeng Wang
2023-11-01 18:13 ` Stephen Hemminger [this message]
2023-11-06 17:04 ` Thomas Monjalon
2023-11-02 9:57 ` Robin Jarry
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=20231101111339.27ecfcd6@fedora \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=kevin.laatz@intel.com \
--cc=mb@smartsharesystems.com \
--cc=nd@arm.com \
--cc=rjarry@redhat.com \
--cc=ruifeng.wang@arm.com \
--cc=stable@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.