Re: [Linuxptp-users] Port option: logMinDelayReqInterval
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
From: Chandra M. <sma...@al...> - 2015-03-17 13:03:04
|
Hi Miroslav, Please elucidate me on the following. 1. Which field in the delay response indicates the value to the slave announed by the master? Is it logMessageInterval? 2. DelayReq packet is sent by the slave. Thus, the number of DelayReq packets to be sent is to be controlled by the slave. Am I right? Why should it be an option with master? An answer to my own question: It is the master being burdened to respond to possibly many number of slaves. Hence, it controls the number. Is this the rationale for what you have mentioned below? Thanking you in anticipation, Regards, Chandra (c) : 0175508142 (O): 701.6412 "Knowledge speaks, Wisdom listens" -----Original Message----- From: Miroslav Lichvar [mailto:mli...@re...] Sent: Tuesday, March 17, 2015 7:34 PM To: Chandra Mallela Cc: Ledda William EXT; lin...@li... Subject: Re: [Linuxptp-users] Port option: logMinDelayReqInterval On Tue, Mar 17, 2015 at 11:18:20AM +0000, Chandra Mallela wrote: > I think I have resolved the issue though not sure whether it is the right way. When I have used the option 'logMinDelayReqInterval -5' in ptp4l.conf at both slave and master (as opposed to just at the slave), I could see that the frequency of delay calculations has increased. Perhaps, at the slave, the option might imply 'number of delay request packets to be sent' and at the master, 'number of delay request packets to be processed'. Only when they match, the ptp4l is taking the option into consideration. That option needs to be set on master. On slaves it sets only the initial value, after receiving first delay response message they will switch to the value announced by the master. -- Miroslav Lichvar ________________________________ Confidentiality Notice. This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you. |