From 8fda6e80c1e9f2c9d4d9d45e5a16e48dea97efce Mon Sep 17 00:00:00 2001 From: Dinesh Neelapu Date: Mon, 24 Jul 2023 14:40:30 +0000 Subject: [PATCH] PTP PMC example and system configuartion changes. (r8) Updated a small change suggested by ron. Change-Id: I574cb950642ae6e96c0e888a7d358a7aa9aed944 Signed-off-by: Dinesh Neelapu --- .../instance-specific-considerations-d9d9509c79dd.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/system_configuration/kubernetes/instance-specific-considerations-d9d9509c79dd.rst b/doc/source/system_configuration/kubernetes/instance-specific-considerations-d9d9509c79dd.rst index ab4727cb5..5c54361f8 100644 --- a/doc/source/system_configuration/kubernetes/instance-specific-considerations-d9d9509c79dd.rst +++ b/doc/source/system_configuration/kubernetes/instance-specific-considerations-d9d9509c79dd.rst @@ -38,7 +38,7 @@ for it to start. designs have a single |PHC| shared between all the ports on the |NIC|, while others may have one |PHC| per port. Refer to the |NIC| documentation to determine if a |NIC| has multiple |PHCs|. Configuring a ``ptp4l`` instance - with multiple interfaces, each with its own |PHC|, results in degraded + with multiple interfaces, each with its own |PHC| results in degraded timing accuracy or other undesirable behaviors. This means that a given ``ptp4l`` instance should only be configured with interfaces that are on the same |NIC| and share a |PHC|.