Sure, the Annex J is silly but the customers ask for it. :( The idea is to keep current and the last snapshot (15m, 1h, 24h) demanding the complete history to the external monitor. Using just polling on UDS is a bad idea IMHO because you need to capture at the exact same time point all counters of all ports spending a lot of effort and cpu. In addition the counters must be gathered in an atomic way in order to be coherent with each other. It's better to have the gathering under the hood and a way to inquiry the system.
Furthermore I will start again on this topic next year, and I'm collecting all the feedback to produce an acceptable solution. luigi Il giorno ven 10 nov 2023 alle ore 06:33 Richard Cochran < richardcoch...@gmail.com> ha scritto: > On Fri, Aug 18, 2023 at 02:34:54PM +0200, Luigi Mantellini wrote: > > Dear All, > > > > Starting from IEEE 1588-2019 Annex J, I'm trying to introduce a > Performace > > monitoring Counters. > > > > The standard asks to keep up 98 records (96 for 15min records and 2 for > 24h > > records). > > > > I tried to follow a more general approach keeping different circular > buffer > > for 15min and 24h (and adding also 1h for test purpose). > > > > The patch need to be split, of course, but it's a starting point to have > any > > feedbacks. > > My only feedback is: > > - the statistics in Annex J are silly, but > > - if you really want those, please write a stand alone program that > gathers the statistics from data input via the UDS interface > > Thanks, > Richard > -- *Luigi 'Comio' Mantellini* My Professional Profile <http://www.linkedin.com/in/comio> *"UNIX is very simple, it just needs a genius to understand its simplicity." [cit.]*
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
