On Thu, Jun 07, 2018 at 11:13:38AM +0000, Anders Selhammer wrote:
> This is more of a question or a clarification if I get it right, but this
> ucma->renewal_tmo is general
> for all types of messages for a ucma.
Right.
> So if announce is granted, this renewal_tmo will be updated to 3/4 of the
> duration that was given
> in grant and state go to HAVE_ANN. Then if the master is not selected
> directly but shortly
> before tmo expires and a new negotiation of announce should occur, then state
> will go to
> NEED_SYDY and negotiation of SYNC and DELAY will occur. Then when one of them
> is granted,
> the state will got to HAVE_SYDY and the renewal_tmo will be updated to 3/4 of
> the duration in grant.
No. See below.
> Then timer expires and unicast_client_renew will be called.
>
> Will not now.tv_sec be less than ucma->renewal_tmo and a new negotiation for
> ANN SYNC and DELAY
> not be sent?
In unicast_client_set_renewal() we take the minimum of the old
renewal_tmo and the new one.
tmo = now.tv_sec + duration;
if (!master->renewal_tmo || tmo < master->renewal_tmo) {
master->renewal_tmo = tmo;
}
Then, when the deadline occurs, we renew everything.
> How should this logQueryInterval should be set?
This comes from the profile and is set in the configuration file.
> Should the timer expire several times during the
> granted negotiated period of messages?
I don't see why not.
> Is the granted negotiation period same for all types of messages?
Not necessarily. It depends on the granting server. Our client
simply renews everything at the earliest deadline in any case.
Thanks,
Richard
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
