| Re: [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: Re: [chrony-users] Hardware timestamping in CentOS 7.4 (was: Possible to get sub-millisecond accuracy?)
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Fri, 23 Jun 2017 17:57:50 +0200
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com B708F7C83B
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com B708F7C83B
On Fri, Jun 23, 2017 at 11:21:29AM -0400, Chris Perl wrote:
> 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?
You would have to patch the code to not try to enable the RX filter.
Currently, if the setting fails, HW timestamping is not used, even if
it could work for TX.
> 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.
That's an interesting idea. Do you think people would prefer SW RX+HW
TX timestamping over SW RX+SW TX?
> Also, perhaps you're not able to answer this question, but any sense
> for when 7.4 will land?
No, sorry.
--
Miroslav Lichvar
--
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.