On Mon, Apr 07, 2014 at 06:02:13PM +0200, Jiri Benc wrote:
> On Sat, 5 Apr 2014 13:02:14 +0200, Richard Cochran wrote:
> > > +struct port_enumeration_np {
> > > + UInteger16 numberPorts;
> > > + UInteger16 portNumber[0];
> > > +} PACKED;
> > > +
> >
> > I don't like this variable sized message. We should stick to fixed
> > sized items. Why do we need this at all?
>
> The idea was to find out easily which ports are available. I wanted to
> omit querying each port number in turn to find out whether it exists or
> not (i.e. it's a "hole").
>
> If you prefer that, or have even better idea, I'm happy to rewrite this.
I prefer the one-by-one query. This isn't a performance critical
operation.
> > BTW, regarding your dynamic port work, have you seen 1588
> > Interpretation 21?
>
> I did not, thanks for the pointer. If I'm reading it correctly, it
> basically matches what I've been expecting.
Okay, fine.
Thanks,
Richard
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
