On Mon, Jan 28, 2019 at 05:24:37PM +0100, Miroslav Lichvar wrote: > Add option unicast_max_message_rate to limit the rate of messages > generated by the unicast service for all contracts of the port. > When a request is received and the current rate of messages is so large > that granting the service would exceed the maximum, deny the request.
Do we really have to set an artificial limit? My original idea was to let the number of client be limited only by the available memory. Paranoid sysadmins can throw ptp4l into a C-group. > The default value is 1024 messages per second, which corresponds to > about 680 clients using the default announce and sync intervals, or 4 > clients using the maximum rate of 128 messages per second. How did you arrive that those numbers? Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
