On Wed, Dec 06, 2023 at 03:43:15PM +0100, Andrew Zaborowski wrote:
> Again feel free to include it or leave it for us to send separately.
I prefer to roll your fixes into this series.
Thanks,
Richard
___
Linuxptp-devel mailing list
On Tue, 5 Dec 2023 at 02:44, Andrew Zaborowski
wrote:
> * if I stop a CMLDS client and rerun it, it will receive the CMLDS
> notifications twice until the old subscription expires. If I restart
> it again quickly enough it'll receive each notification 3 times. This
> is because pmc_recv
On Tue, Dec 05, 2023 at 02:44:18AM +0100, Andrew Zaborowski wrote:
> * if I stop a CMLDS client and rerun it, it will receive the CMLDS
> notifications twice until the old subscription expires. If I restart
> it again quickly enough it'll receive each notification 3 times. This
> is because
On Mon, Dec 04, 2023 at 10:51:15PM +0100, Andrew Zaborowski wrote:
> I assume ignore_transport_specific can be dropped in this version.
Actually it is critical, if you care about being able to
inter-operate. After all, nothing guarantees that the link partner is
also running CMLDS. Experience
I tested a basic 802.1AS type scenario with this v3 patchset on both
ends, and it worked! We may have more test results in a few days if
my colleague runs a real test suite.
The only caveats were:
* if I stop a CMLDS client and rerun it, it will receive the CMLDS
notifications twice until the
On Sun, 3 Dec 2023 at 00:39, Richard Cochran wrote:
> +# Common Mean Link Delay Service (CMLDS) example configuration for a
> +# CMLDS Link Port, containing those attributes which differ from the
While there's only one Link Port here I wouldn't mention this because
the CMLDS config basically has
