From: Stephen Hemminger <stephen@networkplumber.org>
To: Dawid Wesierski <dawid.wesierski@intel.com>
Cc: dev@dpdk.org, reshma.pattan@intel.com, thomas@monjalon.net,
mb@smartsharesystems.com, marek.kasiewicz@intel.com,
Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Zhirun Yan <yanzhirun_163@163.com>
Subject: Re: [PATCH v7] pcapng: add user-supplied timestamp support
Date: Wed, 14 Oct 2026 10:38:58 -0700 [thread overview]
Message-ID: <20261014103858.5a454dac@phoenix.local> (raw)
In-Reply-To: <20261014172102.1090177-1-dawid.wesierski@intel.com>
On Wed, 14 Oct 2026 17:21:01 +0000
Dawid Wesierski <dawid.wesierski@intel.com> wrote:
>
> +RTE_EXPORT_EXPERIMENTAL_SYMBOL(rte_pcapng_tsc_to_ns, 26.11)
> +uint64_t
> +rte_pcapng_tsc_to_ns(const rte_pcapng_t *self, uint64_t tsc)
> +{
> + return pcapng_timestamp(self, tsc);
> +}
> +
Since the tsc_to_ns is independent of the pcapng handle, I had some
patches in other work which made it not require pcapng_open and/or move
it to EAL. What do you think?
prev parent reply other threads:[~2026-10-14 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 14:38 [PATCH v3 1/1] pcapng: add user-supplied timestamp support Dawid Wesierski
2026-06-18 15:22 ` Stephen Hemminger
2026-06-18 16:45 ` Morten Brørup
2026-06-18 18:51 ` Stephen Hemminger
2026-06-23 14:10 ` [PATCH v4] " Dawid Wesierski
2026-06-23 13:53 ` Stephen Hemminger
2026-06-24 21:57 ` [PATCH v5] " Dawid Wesierski
2026-06-24 22:07 ` Stephen Hemminger
2026-06-24 22:17 ` Stephen Hemminger
2026-06-26 10:22 ` [v5] " Dawid Wesierski
2026-06-26 15:04 ` Stephen Hemminger
2026-06-29 9:37 ` [PATCH v6 1/1] " Dawid Wesierski
2026-06-29 16:50 ` Stephen Hemminger
2026-10-14 17:21 ` [PATCH v7] " Dawid Wesierski
2026-10-14 17:38 ` Stephen Hemminger [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=20261014103858.5a454dac@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dawid.wesierski@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=marek.kasiewicz@intel.com \
--cc=mb@smartsharesystems.com \
--cc=ndabilpuram@marvell.com \
--cc=reshma.pattan@intel.com \
--cc=thomas@monjalon.net \
--cc=yanzhirun_163@163.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.