DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Hari Haran <info2hariharan@gmail.com>
Cc: users@dpdk.org
Subject: Re: rte_rdtsc() - what is the performance impact of using rte_rdtsc() time
Date: Tue, 5 Sep 2023 16:29:29 -0700	[thread overview]
Message-ID: <20230905162929.3dbc9e12@hermes.local> (raw)
In-Reply-To: <CAPbxCtrRqXHU772U7eZFoDcKL2pRiE39vgBifWYC96kC04MhiQ@mail.gmail.com>

On Tue, 29 Aug 2023 20:25:54 +0530
Hari Haran <info2hariharan@gmail.com> wrote:

> Hi All,
> 
> Subject: rte_rdtsc() - what is the performance impact of using rte_rdtsc()
> time under lcore thread while(1)
> 
> Requirement:
> 
>    1. Store the packet received timestamp - based on it packets will be
>    removed from buffer if it exceeds the threshold timer of buffer
>    2. Two threads are available, One is lcore(dedicated core) and another
>    is pthread(not a dedicated core. In pthread, have to get the timestamp of
>    last received packet timestamp
> 
> 
> Query:
> 
>    1. For every packet reception in lcore thread under while(1), will get
>    the packet received timestamp using  rte_rdtsc() function. Whether usage of
>    rte_rdtsc() function adds more delay in packet processing?
>    2. Is there any way to convert rte_rdtsc() timestamp value to current
>    system time in pthread()? In pthread, the last packet received time needed
>    in the form of system time.
> 
> 
> Thanks in advance.
> 
> Regards,
> Hariharan

The problem is that rte_rdtsc() stops speculative execution so doing
lots of TSC instructions can hurt performance.

To correlate TSC timestamp to system time, you need to compute the offsets
once at startup. Alternatively, don't use rte_rdtsc() and instead use
clock_gettime() with the monotonic timer and the C library does the calculation
for you.

  reply	other threads:[~2023-09-05 23:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 14:55 Hari Haran
2023-09-05 23:29 ` Stephen Hemminger [this message]
2023-10-03 10:19   ` Hari Haran
2023-10-03 17:17     ` Stephen Hemminger

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=20230905162929.3dbc9e12@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=info2hariharan@gmail.com \
    --cc=users@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).