DPDK usage discussions
 help / color / mirror / Atom feed
From: Isaac Boukris <iboukris@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: dumpcap: timestamp is years ahead when in pcapng format
Date: Wed, 20 Sep 2023 20:59:48 +0300	[thread overview]
Message-ID: <CAC-fF8RnYfO7QrzU5ftG4hqDPchJoUHx9aeW6tmVCdk7JZUJGg@mail.gmail.com> (raw)
In-Reply-To: <20230919110009.29e90615@hermes.local>

On Tue, Sep 19, 2023 at 9:00 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> On Tue, 19 Sep 2023 19:35:55 +0300
> Isaac Boukris <iboukris@gmail.com> wrote:
>
> > Looking with git log, i found the original line was:
> > return pcapng_time.ns + (delta * NSEC_PER_SEC) / rte_get_tsc_hz();
> >
> > Testing that does show a wrapping issue, e.g. (it stays around 08:05).
> >
> > 2023-09-19 08:05:24.372037 IP _gateway.domain > Rocky8.38358: 31975
> > NXDomain 0/0/0 (46)                                              10
> > 2023-09-19 08:05:21.577497 ARP, Request who-has _gateway tell Rocky8,
> > length 46
> > 2023-09-19 08:05:21.577599 ARP, Reply _gateway is-at 00:50:56:f8:92:76
> > (oui Unknown), length 46                                     13
> > 2023-09-19 08:05:22.833897 IP 192.168.202.1.50886 >
> > 239.255.255.250.ssdp: UDP, length 174
> >
> > However with my change it looks fine and always increments. I dropped
> > all the parenthesis:
> > return pcapng_time.ns + delta / pcapng_time.tsc_hz * NSEC_PER_SEC;
>
> The issue is that timestamping is in the fast path and that 64 bit divide is slow.
> Looking at other alternatives.

Then perhaps we can keep the division optimization and just get rid of
the overflow check, relying on the change to multiply by NSEC_PER_SEC
after the division.

With the below change only the first packet is from 2257 while all
subsequent packets are fine. But if I keep the overflow check and only
change to multiply after the division, then all packets are shown from
2257.

[admin@Rocky8 dpdk]$ git diff lib/pcapng/rte_pcapng.c
diff --git a/lib/pcapng/rte_pcapng.c b/lib/pcapng/rte_pcapng.c
index 80d08e1..fa545cd 100644
--- a/lib/pcapng/rte_pcapng.c
+++ b/lib/pcapng/rte_pcapng.c
@@ -79,7 +79,7 @@ static uint64_t pcapng_tsc_to_ns(uint64_t cycles)
         * Currently all TSCs operate below 5GHz.
         */
        delta = cycles - pcapng_time.cycles;
-       if (unlikely(delta >= pcapng_time.tsc_hz)) {
+       if (0 && unlikely(delta >= pcapng_time.tsc_hz)) {
                if (likely(delta < pcapng_time.tsc_hz * 2)) {
                        delta -= pcapng_time.tsc_hz;
                        pcapng_time.cycles += pcapng_time.tsc_hz;
@@ -92,8 +92,9 @@ static uint64_t pcapng_tsc_to_ns(uint64_t cycles)
                }
        }

-       return pcapng_time.ns + rte_reciprocal_divide_u64(delta * NSEC_PER_SEC,
-
&pcapng_time.tsc_hz_inverse);
+       return pcapng_time.ns + rte_reciprocal_divide_u64(delta,
+
&pcapng_time.tsc_hz_inverse) * NSEC_PER_SEC;
 }

  reply	other threads:[~2023-09-20 18:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 14:40 Isaac Boukris
2023-09-19 16:35 ` Isaac Boukris
2023-09-19 18:00   ` Stephen Hemminger
2023-09-20 17:59     ` Isaac Boukris [this message]
2023-09-20 18:53       ` Isaac Boukris
2023-09-20 19:55         ` Isaac Boukris
2023-09-21  2:09           ` Stephen Hemminger
2023-09-21  5:14             ` Isaac Boukris
2023-09-21 15:31               ` Stephen Hemminger
2023-09-21 19:00                 ` Isaac Boukris

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=CAC-fF8RnYfO7QrzU5ftG4hqDPchJoUHx9aeW6tmVCdk7JZUJGg@mail.gmail.com \
    --to=iboukris@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).