| Re: [chrony-users] hwtimestamp |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] hwtimestamp
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 10 Aug 2020 09:59:30 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1597046377; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=DcE1RVnX3joUoWClc5dJAQuFOFGVFrQu85pyJI64qiI=; b=EWqUsF/rj9moEXmrGmAF+d0RDr+KC/sLjgGnBWB1+XYPweHkvZc9/vsMvoS0aqmVnshJ7L aMILBSLHqmuKUJdJqeCC8Jtq/0XVqOC+jwr0tdJY6ivKJxkHyWHL9DTkrsQVKTkHwoEs4L ooSYmDON4XgXlYELFANUSjSIFVGY5VE=
On Sun, Aug 09, 2020 at 12:51:03PM +0100, Nuno Gonçalves wrote:
> I so assume as you say that since this is not working, and the
> hardware does not support non PTP RX timestamps, it is very likely
> that it would not support this on the TX side.
Usually that's not the case, but here it seems to be like that
according to this code:
https://github.com/torvalds/linux/blob/e8407fdeb9a6866784e249881f6c786a0835faba/drivers/net/ethernet/ti/cpts.h#L135
The RX filter is needed when the NIC cannot provide a timestamp
with each packet, so it needs to be told what (rarely received)
packets it should timestamp. Fortunately, it seems the trend with
modern NICs is going away from this limitation.
For TX timestamping, most NICs don't care what packet it is as the
driver can tell the NIC that it should timestamp this particular
packet when it's queued. But with some NICs that doesn't seem to be
possible, so the NIC is timestamping all PTP-event packets and the
driver needs to get check if a timestamp was requested for a
transmitted packet.
A theoretical possibility to get around this limitation would be to
wrap NTP packets in PTP packets in order to match the HW filter in the
NIC if it allows longer packets. Of course, this non-standard PTP/NTP
would need to be supported on both server and client.
--
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.