On Tue, Apr 27, 2021 at 03:59:05PM +0000, Ramana Reddy wrote:
> <Ramana> As I said, running independent clients defeats the purpose of BMC
> algorithm and breaks the ITU-T G.8275.2
> Spec compliance. The BMC algorithm should be run locally on all ports of
> every ordinary and boundary clock in a domain. Since it
> runs continuously, it continually readapts to changes in the network or the
> clocks. Pls check section 9.3 in IEEE1588-2008
> Spec for details on BMC algorithm. Also refer to Section 6.7 of A-BMCA
> requirements of ITU-T G.8275.2 spec.
Did you even read ITU-T G.8275.2 Section 6.7 ?
It makes no mention of slaveOnly, but rather masterOnly and
localPriority.
You have not clearly identified a problem with linuxptp WRT G.8275.2.
If there is a problem, please state it.
> > <Ramana> I believe Ordinary Clock can have multiple ports
No, your belief is incorrect. The number of ports differentiates OC
from BC. In fact, that is the only difference.
> <Ramana> Pls refer my earlier reply for why we need to run single ptp4l
> instance with multiple ports in OC mode.
You _seem_ to be proposing a new and different state machine, not
specified by 1588 or G.8275.2. If you want to do that, fine, but
please develop some kind of design document that explains both the
motivation and the theory of operation.
Then, you can provide the implementation in the modular way that does
not deface the linuxptp architecture.
Hint:
p->state_machine = clock_slave_only(clock) ? ptp_slave_fsm : ptp_fsm;
Thanks,
Richard
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
