From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Tom Barbette <barbette@kth.se>, <dev@dpdk.org>
Cc: <bruce.richardson@intel.com>, <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>, <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/3] rte_ethdev: Add API function to read dev clock
Date: Wed, 8 May 2019 10:54:17 +0300 [thread overview]
Message-ID: <cffcf0ba-9bd4-11eb-1959-e53c7a7e3a49@solarflare.com> (raw)
In-Reply-To: <20190502121135.18775-2-barbette@kth.se>
On 5/2/19 3:11 PM, Tom Barbette wrote:
> Add rte_eth_read_clock to read the raw clock of a device.
>
> The main use is to get the device clock conversion co-efficients to be
> able to translate the raw clock of the timestamp field of the pkt mbuf
> to a local synced time value.
>
> This function was missing to allow users to convert the Rx timestamp field
> to real time without the complexity of the rte_timesync* facility. One can
> derivate the clock frequency by calling twice read_clock and then keep a
> common time base.
>
> Signed-off-by: Tom Barbette <barbette@kth.se>
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2019-05-08 7:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 12:11 [dpdk-dev] [PATCH v4 0/3] Add rte_eth_read_clock API Tom Barbette
2019-05-02 12:11 ` Tom Barbette
2019-05-02 12:11 ` [dpdk-dev] [PATCH v4 1/3] rte_ethdev: Add API function to read dev clock Tom Barbette
2019-05-02 12:11 ` Tom Barbette
2019-05-08 7:54 ` Andrew Rybchenko [this message]
2019-05-08 7:54 ` Andrew Rybchenko
2019-06-04 13:57 ` Ferruh Yigit
2019-05-02 12:11 ` [dpdk-dev] [PATCH v4 2/3] mlx5: Implement support for read_clock Tom Barbette
2019-05-02 12:11 ` Tom Barbette
2019-05-02 12:11 ` [dpdk-dev] [PATCH v4 3/3] rxtx_callbacks: Add support for HW timestamp Tom Barbette
2019-05-02 12:11 ` Tom Barbette
2019-05-31 7:46 ` Ferruh Yigit
2019-06-13 5:55 ` Thomas Monjalon
2019-05-08 7:49 ` [dpdk-dev] [PATCH v4 0/3] Add rte_eth_read_clock API Tom Barbette
2019-05-08 7:49 ` Tom Barbette
2019-05-31 7:46 ` Ferruh Yigit
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=cffcf0ba-9bd4-11eb-1959-e53c7a7e3a49@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=barbette@kth.se \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=olivier.matz@6wind.com \
--cc=shahafs@mellanox.com \
--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).