Richard Cochran <richardcoch...@gmail.com> > This series completes the unicast and telecom support by adding the > server side of the equation. The first patch introduces a priority > queue in order to service any number of clients, each with its own > interval (as required by the telecom profile). In that way we can > multiplex many clients using a single timer. For the sake of > efficiency, each different interval is modeled as a single instance, > and the client addresses hang off of the intervals.
Hi When are you planning to merge the unicast and telecom support? I guess you are doing some updates after review but I have not seen any major comments regarding these three series. The reason I ask is that we are hungry to test this in our lab and see how well it behaves. Do you think it will be merged before end of July? I also have one question regarding resource management of the uc server side. All requests are granted unless there are some allocation problem. What if there are limitations such as maximum number of slaves or maximum number of packets / second that the system can handle? Are there any plans of adding a possibility to add some limitations or will that be up to the user to add if needed? /Anders ------------------------------------------------------------------------------ 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
