Hi all, We are doing some research based on ptp4l and I noticed that it doesn’t perform delay estimation and offset estimation on the same cycle. That is, the client updates only the estimated delay when it receives a DELAY_RESP and then updates the offset estimation (and corrects the clock) when receiving next cycle’s SYNC message. Is there a specific reasoning behind this implementation decision?
I actually tried my hand at changing the code locally so it does everything on the same cycle (both delay and offset estimation when receiving a DELAY_RESP) and, although it works, performance is noticeably worse than the base ptp4l implementation. This is the issue I’m trying to figure out. Best regards, Víctor _ Víctor Vázquez PhD Student Department of Computer Engineering, Automatics and Robotics (ICAR) Time-based Technologies and Networks Lab University of Granada Calle Periodista Rafael Gómez Montero, 2 CITIC-UGR, Office D1-2 18014 Granada, Spain
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
