From: Thomas Monjalon <thomas@monjalon.net>
To: Omar Awaysa <omara@nvidia.com>
Cc: dev@dpdk.org, rasland@nvidia.com,
Raja Zidane <rzidane@nvidia.com>,
stable@dpdk.org
Subject: Re: [PATCH v2] examples/link_status_interrupt: fix stats refresh rate
Date: Fri, 08 Jul 2022 16:47:12 +0200 [thread overview]
Message-ID: <5589546.vanWaX58re@thomas> (raw)
In-Reply-To: <20220707082234.2787-1-omara@nvidia.com>
07/07/2022 10:22, Omar Awaysa:
> From: Raja Zidane <rzidane@nvidia.com>
>
> TIMER_MILLISECOND is defined as the number of cpu cycles per millisecond,
> current definition is correct for cores with frequency of 2GHZ, for cores
> with different frequency, it caused different periods between refresh,
> (i.e. the definition is about 14ms on ARM cores).
>
> Use dpdk API to get CPU frequency, to define TIMER_MILLISECOND.
>
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: Omar Awaysa <omara@nvidia.com>
Applied (with indent fixed), thanks.
prev parent reply other threads:[~2022-07-08 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 9:37 [PATCH] " Raja Zidane
2022-06-26 21:22 ` Thomas Monjalon
2022-07-07 8:22 ` [PATCH v2] " Omar Awaysa
2022-07-08 14:47 ` Thomas Monjalon [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=5589546.vanWaX58re@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=omara@nvidia.com \
--cc=rasland@nvidia.com \
--cc=rzidane@nvidia.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).