DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chengchang Tang <tangchengchang@huawei.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Min Hu (Connor)" <humin29@huawei.com>
Cc: <dev@dpdk.org>, <ferruh.yigit@intel.com>, <rsanford@akamai.com>,
	<erik.g.carrillo@intel.com>, <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/timer: fix incorrect time interval
Date: Thu, 22 Apr 2021 09:38:42 +0800	[thread overview]
Message-ID: <dda69a2f-3e96-5b1d-755e-77aab9f756e3@huawei.com> (raw)
In-Reply-To: <2073087.ahSVXVslbx@thomas>

Hi
On 2021/4/22 2:34, Thomas Monjalon wrote:
> 15/04/2021 09:12, Min Hu (Connor):
>> From: Chengchang Tang <tangchengchang@huawei.com>
>>
>> Timer sample example assumes that the frequency of the timer is about
>> 2Ghz to control the period of calling rte_timer_manage(). But this
>> assumption is easy to fail. For example. the frequency of tsc on ARM64
>> is much less than 2Ghz.
> 
> So rte_timer_manage() will be called less often, yes.
> 
>> This patch uses the frequency of the current timer to calculate the
>> correct time interval to ensure consistent result on all platforms.
> 
> I am not sure about making the example more complex.
> What is the issue with the previous value?
>
In my understanding, the example should illustrate the standard usage of
related functions. Some of our customers did not know the difference in
tsc frequency between arm and x86 when using our SoC. As a result, some
misunderstanding are caused. So I think I could explain a more general
approach in the example, which will help these new users. When using a
timer, we must first know its frequency.  So I've added a frequency
acquisition process to the example, so that new users can realize that
there are differences between different platforms, so that they can design
more general programs.

>
> 
> 
> .
> 


  reply	other threads:[~2021-04-22  1:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  7:12 Min Hu (Connor)
2021-04-21 18:34 ` Thomas Monjalon
2021-04-22  1:38   ` Chengchang Tang [this message]
2021-04-21 19:12 ` Carrillo, Erik G
2021-05-05 21:37 ` Thomas Monjalon
2021-05-06  2:06   ` Chengchang Tang
2021-05-06  8:08     ` Thomas Monjalon
2021-05-06  8:23       ` Chengchang Tang
2021-05-06  9:29 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-05-12 14: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=dda69a2f-3e96-5b1d-755e-77aab9f756e3@huawei.com \
    --to=tangchengchang@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=ferruh.yigit@intel.com \
    --cc=humin29@huawei.com \
    --cc=rsanford@akamai.com \
    --cc=thomas@monjalon.net \
    /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).