From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <stable-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
by inbox.dpdk.org (Postfix) with ESMTP id 3212CA00C5
for <public@inbox.dpdk.org>; Fri, 8 Jul 2022 16:47:18 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 155154021E;
Fri, 8 Jul 2022 16:47:18 +0200 (CEST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
[66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 986ED4021E;
Fri, 8 Jul 2022 16:47:16 +0200 (CEST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46])
by mailout.nyi.internal (Postfix) with ESMTP id D4F565C01A9;
Fri, 8 Jul 2022 10:47:14 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
by compute2.internal (MEProxy); Fri, 08 Jul 2022 10:47:14 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
cc:cc:content-transfer-encoding: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=fm3; t=1657291634; x=
1657378034; bh=FTYUdKj/1g5pKxQ9fKChIwxT2iBwbGX55Ke+g5nS6CU=; b=I
0orjMInM52d0NSuetFNte9dE763fmB6l6fNe2hIYEXxlNBY4mMJSqtwPSq5plDGv
2AEP061zm8nsqEHpNHDOA17fziS+luqBBmnhPf08+o0lEjxvCLuLZYnG8EiU0dal
ITFFa5mxzLT1pxNl5LquTFWY0oKkrp+wsCwne29s3TZEDx/9tbMCJvXc5XKYBQOO
W0SiZr3QKHuglkiFBlzzQ+I68yZn2BufRpdGqmARa5Tqd9Y4CseXabxcuPyjzRPL
YYQ0UXbi20EFtktwODXoG60c4InA1/QeQckwM6bDKi6CxG+CI+JnPznU4pX7l0hr
buC0v/lzcSxEDELIK6TwQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=cc:cc:content-transfer-encoding
: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=fm3; t=1657291634; x=
1657378034; bh=FTYUdKj/1g5pKxQ9fKChIwxT2iBwbGX55Ke+g5nS6CU=; b=v
glH8LJ5hStKkQhrcNqx6IYMJQu0fk4P1I/1OnZrwiv9/iLePexxM2MFTNbIxrMeo
oFrH0Wcl6tIR8L64blOg8CGhksvgkCB8Df40bbPqhubTV9vF5Yzolxr5YrahMn+H
53EORztf675j28Q/1CtrMybMWYa+qJjejkcF/ddhciFIxYgO715vhEtmo/xnEXzF
kPwdfSiuPStcy3ZxPXbeBPPgtXV5la+WlCta0wsrdtiQ+ym9+87aef3Lz/+a8ZAZ
gSZKZQOh4qQKAXJSmOkZ128kesNsTtkaZRCAO0QL5QX6dFjo0tyq0awtGPCuG8ro
C5zh6VokC7I2fVmPI9Kjw==
X-ME-Sender: <xms:ckPIYqbWvzAcXjfKoI792CW_Fd7ToR5POBtDFuU_dwJYftEyLRLUkg>
<xme:ckPIYtakhTkN07UQwQDSea1x7qiuHu0ccUSvuYOAfpqyBni5OyjwcjiWFJyworwNg
3ySOkz9PSDzlDJsEw>
X-ME-Received: <xmr:ckPIYk_LpxD5HiLApO3tRvDPceP03Kbmq5EMmr_b6kHix1mQDcZEFC8URKdF1J3MsUSfXOzBv000Vz05ROF6TJRIvQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeijedgkeduucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne
cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm
rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc
ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei
kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh
hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght
X-ME-Proxy: <xmx:ckPIYsr20QvRVHJ8sEoJfEQKPuOfJE5y5MbRc2c0L_b4srLO3ZYQhA>
<xmx:ckPIYlpUm5bcdY30jUcLUCoMZ6TspeZCUeLeh8vrM07mCgrrdUrUzA>
<xmx:ckPIYqRiyv2BnBcZaQeow7GYfnxKf5pieFh3gP9wVGcdYuqZr7wB7g>
<xmx:ckPIYsX4tm3Ssxmtc_z9I_eVGY2E6jnSH-DO9aPjNvoiKb9WTgQWtg>
Feedback-ID: i47234305:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri,
8 Jul 2022 10:47:13 -0400 (EDT)
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
Message-ID: <5589546.vanWaX58re@thomas>
In-Reply-To: <20220707082234.2787-1-omara@nvidia.com>
References: <20220530093702.11745-1-rzidane@nvidia.com>
<20220707082234.2787-1-omara@nvidia.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: patches for DPDK stable branches <stable.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/stable>,
<mailto:stable-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/stable/>
List-Post: <mailto:stable@dpdk.org>
List-Help: <mailto:stable-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/stable>,
<mailto:stable-request@dpdk.org?subject=subscribe>
Errors-To: stable-bounces@dpdk.org
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.