[Linuxptp-users] High path delay: i219 vs i210?

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hello,</div>

<div>&nbsp;</div>

<div>I have a problem with the high of the calculated path delay. I am using hardware timestamping and thought I get values less than 20ns. But i have values over 7.8&micro;s is that normal?<br/>
I have also tested the usecase with an i210, there I got 250ns,&nbsp;but these are also quite high.</div>

<div>&nbsp;</div>

<div>Questions:</div>

<div>1. why are the values of i219 and i210 so different?&nbsp;what does the path delay depend on?<br/>
2. if it depends only on the NIC, where can I find out which NIC&nbsp;is the best one for hardware time stamping, which keywords in the datasheet are important?&nbsp;<br/>
3. Is there a driver problem or is it possible to change something at the ptp-files to get better values?</div>

<div>&nbsp;</div>

<div>NIC: I2019-V rev 21<br/>
driver: e1000e - 3.8.4-NAPI</div>

<div>Kernel:5.4.0-104-generic</div>

<div>&nbsp;</div>

<div>output of: ethtool -T enp0s31f6:<br/>
Time stamping parameters for enp0s31f6:<br/>
Capabilities:<br/>
&nbsp; &nbsp; &nbsp; &nbsp; hardware-transmit &nbsp; &nbsp; (SOF_TIMESTAMPING_TX_HARDWARE)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; software-transmit &nbsp; &nbsp; (SOF_TIMESTAMPING_TX_SOFTWARE)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; hardware-receive &nbsp; &nbsp; &nbsp;(SOF_TIMESTAMPING_RX_HARDWARE)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; software-receive &nbsp; &nbsp; &nbsp;(SOF_TIMESTAMPING_RX_SOFTWARE)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; software-system-clock (SOF_TIMESTAMPING_SOFTWARE)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; hardware-raw-clock &nbsp; &nbsp;(SOF_TIMESTAMPING_RAW_HARDWARE)<br/>
PTP Hardware Clock: 0<br/>
Hardware Transmit Timestamp Modes:<br/>
&nbsp; &nbsp; &nbsp; &nbsp; off &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (HWTSTAMP_TX_OFF)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; on &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(HWTSTAMP_TX_ON)<br/>
Hardware Receive Filter Modes:<br/>
&nbsp; &nbsp; &nbsp; &nbsp; none &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(HWTSTAMP_FILTER_NONE)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; all &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (HWTSTAMP_FILTER_ALL)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv1-l4-sync &nbsp; &nbsp; &nbsp; &nbsp; (HWTSTAMP_FILTER_PTP_V1_L4_SYNC)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv1-l4-delay-req &nbsp; &nbsp;(HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-l4-sync &nbsp; &nbsp; &nbsp; &nbsp; (HWTSTAMP_FILTER_PTP_V2_L4_SYNC)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-l4-delay-req &nbsp; &nbsp;(HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-l2-sync &nbsp; &nbsp; &nbsp; &nbsp; (HWTSTAMP_FILTER_PTP_V2_L2_SYNC)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-l2-delay-req &nbsp; &nbsp;(HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-event &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (HWTSTAMP_FILTER_PTP_V2_EVENT)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-sync &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(HWTSTAMP_FILTER_PTP_V2_SYNC)<br/>
&nbsp; &nbsp; &nbsp; &nbsp; ptpv2-delay-req &nbsp; &nbsp; &nbsp; (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ)</div>

<div><br/>
I use a&nbsp;i219-Notebook with following command as a slave: sudo ptp4l -P -H -l 7 -i enp0s31f6 -m -s<br/>
The &quot;Master&quot;-command is simmiliar just with another interface and without -s.</div>

<div>Output:<br/>
ptp4l[183917.707]: selected best master clock 70ff76.fffe.1dea84<br/>
ptp4l[183917.707]: port 1 (enp0s31f6): LISTENING to UNCALIBRATED on RS_SLAVE<br/>
ptp4l[183918.444]: port 1 (enp0s31f6): delay timeout<br/>
ptp4l[183918.445]: delay &nbsp; filtered &nbsp; &nbsp; &nbsp; 7358 &nbsp; raw &nbsp; &nbsp; &nbsp; 7319<br/>
ptp4l[183918.707]: master offset &nbsp; &nbsp; 239333 s0 freq &nbsp;+45884 path delay &nbsp; &nbsp; &nbsp;7858<br/>
ptp4l[183919.444]: port 1 (enp0s31f6): delay timeout<br/>
ptp4l[183919.445]: delay &nbsp; filtered &nbsp; &nbsp; &nbsp; 7358 &nbsp; raw &nbsp; &nbsp; &nbsp; 7422<br/>
ptp4l[183919.707]: master offset &nbsp; &nbsp; 239368 s1 freq &nbsp;+45919 path delay &nbsp; &nbsp; &nbsp;7858<br/>
ptp4l[183920.444]: port 1 (enp0s31f6): delay timeout<br/>
ptp4l[183920.445]: delay &nbsp; filtered &nbsp; &nbsp; &nbsp; 7349 &nbsp; raw &nbsp; &nbsp; &nbsp; 7345<br/>
ptp4l[183920.708]: master offset &nbsp; &nbsp; &nbsp; -464 s2 freq &nbsp;+45455 path delay &nbsp; &nbsp; &nbsp;7849<br/>
ptp4l[183920.708]: port 1 (enp0s31f6): UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED<br/>
ptp4l[183921.445]: port 1 (enp0s31f6): delay timeout<br/>
ptp4l[183921.445]: delay &nbsp; filtered &nbsp; &nbsp; &nbsp; 7349 &nbsp; raw &nbsp; &nbsp; &nbsp; 7336<br/>
ptp4l[183921.709]: master offset &nbsp; &nbsp; &nbsp; -485 s2 freq &nbsp;+45295 path delay &nbsp; &nbsp; &nbsp;7849<br/>
ptp4l[183922.445]: port 1 (enp0s31f6): delay timeout<br/>
ptp4l[183922.446]: delay &nbsp; filtered &nbsp; &nbsp; &nbsp; 7349 &nbsp; raw &nbsp; &nbsp; &nbsp; 7365<br/>
ptp4l[183922.709]: master offset &nbsp; &nbsp; &nbsp; &nbsp; 27 s2 freq &nbsp;+45661 path delay &nbsp; &nbsp; &nbsp;7849<br/>
ptp4l[183923.445]: port 1 (enp0s31f6): delay timeout<br/>
ptp4l[183923.446]: delay &nbsp; filtered &nbsp; &nbsp; &nbsp; 7340 &nbsp; raw &nbsp; &nbsp; &nbsp; 7330<br/>
ptp4l[183923.709]: master offset &nbsp; &nbsp; &nbsp; &nbsp;137 s2 freq &nbsp;+45779 path delay &nbsp; &nbsp; &nbsp;7840</div>

<div><br/>
&nbsp;</div></div></body></html>

[Linuxptp-users] High path delay: i219 vs i210?

PTP IEEE 1588 stack for Linux

[Linuxptp-users] High path delay: i219 vs i210?