From: zr@semihalf.com
To: barbette@kth.se, dev@dpdk.org
Cc: Zyta Szpak <zr@semihalf.com>
Subject: Re: [dpdk-dev] [RFC PATCH 0/3] Add rte_eth_read_clock API
Date: Wed, 5 Dec 2018 17:33:20 +0100 [thread overview]
Message-ID: <1544027600-9390-1-git-send-email-zr@semihalf.com> (raw)
In-Reply-To: <1543398732-79439-2-git-send-email-barbette@kth.se>
From: Zyta Szpak <zr@semihalf.com>
I'd ask few questions: how is this new rte_ethdev_read_clock different from existing rte_eth_timesync_read_time ?
Is it that this new function does not convert the clock raw value into timespec? Would it be too much overhead to use the timespec type of value? Or do they intent to read different clocks?
next prev parent reply other threads:[~2018-12-05 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 9:52 Tom Barbette
2018-11-28 9:52 ` [dpdk-dev] [RFC PATCH 1/3] rte_ethdev: Add API function to read dev clock Tom Barbette
2018-12-05 16:33 ` zr [this message]
2018-12-08 12:07 ` [dpdk-dev] [RFC PATCH 0/3] Add rte_eth_read_clock API Tom Barbette
2018-12-09 6:00 ` [dpdk-dev] [RFC PATCH 1/3] rte_ethdev: Add API function to read dev clock Shahaf Shuler
2018-11-28 9:52 ` [dpdk-dev] [RFC PATCH 2/3] mlx5: Implement support for read_clock Tom Barbette
2018-12-09 6:03 ` Shahaf Shuler
2018-11-28 9:52 ` [dpdk-dev] [RFC PATCH 3/3] rxtx_callbacks: Add support for HW timestamp 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=1544027600-9390-1-git-send-email-zr@semihalf.com \
--to=zr@semihalf.com \
--cc=barbette@kth.se \
--cc=dev@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).