From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Krzewinski, Piotr" <piotr.krzewinski@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"mattias.ronnblom@ericsson.com" <mattias.ronnblom@ericsson.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] service: fix getting service lcore attributes
Date: Fri, 20 Dec 2024 15:56:38 +0000 [thread overview]
Message-ID: <PH8PR11MB68035924C0B384B56DB3F924D7072@PH8PR11MB6803.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20241220142938.1300646-1-piotr.krzewinski@ericsson.com>
[-- Attachment #1: Type: text/plain, Size: 2382 bytes --]
> From: Piotr Krzewinski <piotr.krzewinski@ericsson.com>
> Sent: Friday, December 20, 2024 2:29 PM
> To: Van Haaren, Harry <harry.van.haaren@intel.com>
> Cc: dev@dpdk.org <dev@dpdk.org>; Krzewinski, Piotr <piotr.krzewinski@ericsson.com>; mattias.ronnblom@ericsson.com <mattias.ronnblom@ericsson.com>; stable@dpdk.org <stable@dpdk.org>
> Subject: [PATCH] service: fix getting service lcore attributes
>
> Perf test service_perf_autotest was failing after introduction
> of lcore variables. Fixed getting of idle_ and error_ service
> call statistics.
>
> Fixes: b24bbaedbba2 ("service: keep per-lcore state in lcore variable")
> Cc: mattias.ronnblom@ericsson.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Piotr Krzewinski <piotr.krzewinski@ericsson.com>
Thanks - verified that these two occurrences were the last two of such kind in the file too!
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
Side-note; seems CI flagged a warning, but not a real issue, artifact is empty
https://lab.dpdk.org/results/dashboard/patchsets/32181/
https://lab.dpdk.org/results/dashboard/testruns/logs/1492956/
> ---
> lib/eal/common/rte_service.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lib/eal/common/rte_service.c b/lib/eal/common/rte_service.c
> index dad3150df9..1821746337 100644
> --- a/lib/eal/common/rte_service.c
> +++ b/lib/eal/common/rte_service.c
> @@ -879,7 +879,7 @@ lcore_attr_get_service_calls(uint32_t service_id, unsigned int lcore)
> static uint64_t
> lcore_attr_get_service_idle_calls(uint32_t service_id, unsigned int lcore)
> {
> - struct core_state *cs = &lcore_states[lcore];
> + struct core_state *cs = RTE_LCORE_VAR_LCORE(lcore, lcore_states);
>
> return rte_atomic_load_explicit(&cs->service_stats[service_id].idle_calls,
> rte_memory_order_relaxed);
> @@ -888,7 +888,7 @@ lcore_attr_get_service_idle_calls(uint32_t service_id, unsigned int lcore)
> static uint64_t
> lcore_attr_get_service_error_calls(uint32_t service_id, unsigned int lcore)
> {
> - struct core_state *cs = &lcore_states[lcore];
> + struct core_state *cs = RTE_LCORE_VAR_LCORE(lcore, lcore_states);
>
> return rte_atomic_load_explicit(&cs->service_stats[service_id].error_calls,
> rte_memory_order_relaxed);
> --
> 2.36.0
[-- Attachment #2: Type: text/html, Size: 11553 bytes --]
prev parent reply other threads:[~2024-12-20 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 14:29 Piotr Krzewinski
2024-12-20 15:56 ` Van Haaren, Harry [this message]
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=PH8PR11MB68035924C0B384B56DB3F924D7072@PH8PR11MB6803.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=mattias.ronnblom@ericsson.com \
--cc=piotr.krzewinski@ericsson.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 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).