| 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: Fri, 31 Jul 2020 10:48:22 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1596185308; 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=0vo6fTdPuqwPif01um8Gd5r3ypxGGD7bjjkKwuCJ59w=; b=FZGUr3f7LkJErXNjxLirtNYa8WURFTApa9364D4Ea5dhzoRJVBmaUclVgQ+IOb52ubAAAp y2szTyCJnSCxMOwrNq29y54zGJxKKMRMwwB9cGcxffIMhDLY0pZ31TzxMVI5JW2aHtNILv FzsmPx0M20hyYv9N+wtak4Pg+v7qzGA=
On Wed, Jul 29, 2020 at 07:12:20AM +0200, Nuno Gonçalves wrote:
> On journal I see chronyd[980]: Enabled HW timestamping (TX only) on eth0.
>
> And having two devices with the same configuration pooling each other
> with noselect I get in the measurements.log MTxRx always "4B K K".
>
> Something missing or this is what is expected with "HW timestamping (TX only)"?
No, that doesn't look right. There should be an "H" in the log, at
least for some entries. What NIC driver does it use? Does it work with
ptp4l? Maybe the HW can get a transmit HW timestamp only for PTP
packets. A Broadcom 10gb NIC has this weird limitation, which cannot
be described in the Linux timestamping API.
--
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.