> -----Original Message-----
> From: Keller, Jacob E [mailto:jacob.e.kel...@intel.com]
> Sent: Friday, August 18, 2017 5:26 PM
> To: Richard Cochran <richardcoch...@gmail.com>; linuxptp-
> de...@lists.sourceforge.net
> Subject: Re: [Linuxptp-devel] [PATCH RFC 07/11] telecom: Add a configuration
> option for defaultDS.localPriority.
> 
> 
> 
> > -----Original Message-----
> > From: Richard Cochran [mailto:richardcoch...@gmail.com]
> > Sent: Friday, August 18, 2017 2:00 PM
> > To: linuxptp-devel@lists.sourceforge.net
> > Subject: [Linuxptp-devel] [PATCH RFC 07/11] telecom: Add a configuration
> option
> > for defaultDS.localPriority.
> 
> > +.B defaultDS.localPriority
> > +The Telecom Profile (ITU-T G.8275.1) specifies an alternate Best
> > +Master Clock Algorithm (BMCA) with a unique data set comparison
> > +algorithm.  The value of this option is associated with the local
> > +clock and is used as a tie breaker whenever clockClass, clockAccuracy,
> > +offsetScaledLogVariance, and priority2 are equal. This option is only
> > +used when "dataset_comparison" is set to "telecom".
> > +The default value is 128.
> 
> Would it make sense to subspace this into something like
> defaultDS.telecom.localPriority?
> 
> Is that even possible?
> 
> Thanks,
> Jake
> 

I realized "defaultDS" probably means "default Domain Specific", which is good 
enough for me. I just wanted a way to make sure that the option name itself 
conveys that it's not going to work in the regular setup.

Thanks,
Jake


------------------------------------------------------------------------------
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
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to