From: Tom Barbette <barbette@kth.se>
To: "Wiles, Keith" <keith.wiles@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dpdk-dev <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Add rte_eth_read_clock API
Date: Wed, 27 Mar 2019 17:08:04 +0100 [thread overview]
Message-ID: <650d6a84-0f8c-c750-afe3-500c91610a67@kth.se> (raw)
Message-ID: <20190327160804.mzDuCjR99HGXlA4yN_awB7DNCD-wEVQ1OnQ7QGpSdjs@z> (raw)
In-Reply-To: <3652C395-2CA3-4F74-BD45-0F06386633FB@intel.com>
On 2019-03-27 15:54, Wiles, Keith wrote:
> I know the API rte_eht_read_clock() is attempting to read the NIC for this timestamp, but if the PMD does not support this request can we just default to the rte_rdtsc() as a return value?
I would not advise that, because the goal of the function is to have
something that is from the same unit than the hardware timestamp given
in the mbufs.
> The current timestamp API is a mess because not all devices behave the
> same way. Trying to write an application that uses timestamping is
> therefore
> very difficult.
This is different than timesync, no other devices implement hardware
timestamping. For me, it's a different feature.
Cheers,
Tom
next prev parent reply other threads:[~2019-03-27 16:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 6:19 Tom Barbette
2019-03-27 6:19 ` Tom Barbette
2019-03-27 6:19 ` [dpdk-dev] [PATCH v2 1/3] rte_ethdev: Add API function to read dev clock Tom Barbette
2019-03-27 6:19 ` Tom Barbette
2019-04-02 17:46 ` Ferruh Yigit
2019-04-02 17:46 ` Ferruh Yigit
2019-04-02 19:24 ` Tom Barbette
2019-04-02 19:24 ` Tom Barbette
2019-03-27 6:19 ` [dpdk-dev] [PATCH v2 2/3] mlx5: Implement support for read_clock Tom Barbette
2019-03-27 6:19 ` Tom Barbette
2019-04-02 17:47 ` Ferruh Yigit
2019-04-02 17:47 ` Ferruh Yigit
2019-04-02 18:26 ` Ferruh Yigit
2019-04-02 18:26 ` Ferruh Yigit
2019-04-02 19:05 ` Tom Barbette
2019-04-02 19:05 ` Tom Barbette
2019-04-03 5:28 ` Shahaf Shuler
2019-04-03 5:28 ` Shahaf Shuler
2019-03-27 6:19 ` [dpdk-dev] [PATCH v2 3/3] rxtx_callbacks: Add support for HW timestamp Tom Barbette
2019-03-27 6:19 ` Tom Barbette
2019-04-02 18:22 ` Ferruh Yigit
2019-04-02 18:22 ` Ferruh Yigit
2019-04-02 19:39 ` Tom Barbette
2019-04-02 19:39 ` Tom Barbette
2019-03-27 14:41 ` [dpdk-dev] [PATCH v2 0/3] Add rte_eth_read_clock API Stephen Hemminger
2019-03-27 14:41 ` Stephen Hemminger
2019-03-27 14:48 ` Thomas Monjalon
2019-03-27 14:48 ` Thomas Monjalon
2019-03-27 14:54 ` Wiles, Keith
2019-03-27 14:54 ` Wiles, Keith
2019-03-27 16:08 ` Tom Barbette [this message]
2019-03-27 16:08 ` Tom Barbette
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=650d6a84-0f8c-c750-afe3-500c91610a67@kth.se \
--to=barbette@kth.se \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=keith.wiles@intel.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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 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).