| [chrony-users] Hardware timestamping in CentOS 7.4 (was: Possible to get sub-millisecond accuracy?) |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Hardware timestamping in CentOS 7.4 (was: Possible to get sub-millisecond accuracy?)
- From: Chris Perl <cperl@xxxxxxxxxxxxxx>
- Date: Fri, 23 Jun 2017 11:21:29 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=7m6IZGpbcCFtthrG176uqMnpDkhMIdsqn82kgO/7FIc=; b=Y7Tzfl5/J7ojQQeFqPBC7e9ZhBZj3oR/CJ/E80iM6hgKsd43SKNSO1D/v9WVXZF4sp LIcdGkk8JbNHq6ju52sqMGe5a9wRLHF1I1VIWLKm1nimi081fcXcYCSd98iKW2+G//nA Pt4NOn7SMgLtfANelNPoKTVNQZw110mt2NOg8=
I decided to improve the subject for any ongoing discussion around
hardware timestamping in 7.4.
On Thu, Jun 15, 2017 at 9:15 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> No, that won't work. The filter applies to received packets. If an
> interface doesn't have HWTSTAMP_FILTER_ALL, it can still generate
> transmit timestamps and chronyd won't know from which interface it
> came.
Ah, makes sense.
When 7.4 lands (and/or on 7.3 using your copr repo if there is only
one card), if I have a card that doesn't support HWTSTAMP_FILTER_ALL,
will I be able to use hardware timestamping for the transmit
timestamps and use kernel timestamping for the receives?
I just wasn't sure if chrony would require both in order to enable
hardware timestamping, or if it would be able to operate with either,
depending on what it finds.
Also, perhaps you're not able to answer this question, but any sense
for when 7.4 will land?
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.