On 9/19/2021 8:49 AM, Georg Sauthoff wrote: > Hello, > > I noticed that starting a DPDK app on one NIC messes with the PTP clock of > another NIC, on a Atom C3758 system with 4 integrated NICs (X553). > > So basically the DPDK initialization changes the other PTP clock's offset > by 100 seconds or so. > > Is this to be expected with the X553 hardware/ixgbe vfio dpdk driver? > > Or is this a bug? > > > Some details: > > lspci | grep Eth > 05:00.0 Ethernet controller: Intel Corporation Ethernet Connection X553 1GbE > (rev 11) > 05:00.1 Ethernet controller: Intel Corporation Ethernet Connection X553 1GbE > (rev 11) > 06:00.0 Ethernet controller: Intel Corporation Ethernet Connection X553 1GbE > (rev 11) > 06:00.1 Ethernet controller: Intel Corporation Ethernet Connection X553 1GbE > (rev 11) > > > The second device (eno2) is bound to dpdk like this: > /opt/dpdk-20.11.2/bin/dpdk-devbind.py --bind vfio-pci 05:00.1 > > The NICs have 2 PTP clocks: > > for i in 1 3 4; do echo $i $(ethtool -T eno$i | grep Clock); done > 1 PTP Hardware Clock: 0 > 3 PTP Hardware Clock: 1 > 4 PTP Hardware Clock: none > > I'm a bit surprised that eno4 don't have a PTP clock, perhaps it's > shared with eno3 - but then the line should read > '4 PTP Hardware Clock: 1', shouldn't it? >
As far as I am aware, the X553 device should have separate clocks for each device it reports.... > I'm running phc2sys like this: > > taskset -c 6 phc2sys -s CLOCK_REALTIME -c /dev/ptp1 -E linreg -m -q -O0 -S > 0.00002 > phc2sys[20652.182]: /dev/ptp1 sys offset -27 s0 freq -24325 delay > 2251 > phc2sys[20653.182]: /dev/ptp1 sys offset -29 s0 freq -24325 delay > 2249 > phc2sys[20654.182]: /dev/ptp1 sys offset 11 s0 freq -24325 delay > 2300 > phc2sys[20655.182]: /dev/ptp1 sys offset -20 s2 freq -24326 delay > 2245 > phc2sys[20656.182]: /dev/ptp1 sys offset -15 s2 freq -24336 delay > 2251 > [..] > phc2sys[20668.184]: /dev/ptp1 sys offset -34 s2 freq -24328 delay > 2251 > phc2sys[20669.184]: /dev/ptp1 sys offset -92 s2 freq -24376 delay > 2261 > phc2sys[20670.184]: /dev/ptp1 sys offset 17 s2 freq -24300 delay > 2261 > phc2sys[20671.184]: /dev/ptp1 sys offset -63 s2 freq -24351 delay > 2251 > <-- simple DPDK application is started > phc2sys[20672.184]: clockcheck: clock jumped backward or running slower than > expected! > phc2sys[20672.184]: /dev/ptp1 sys offset -500186598241 s0 freq -24351 delay > 2249 > phc2sys[20673.184]: /dev/ptp1 sys offset -500186598213 s0 freq -24351 delay > 2248 > phc2sys[20674.184]: /dev/ptp1 sys offset -500186598126 s0 freq -24351 delay > 2248 > phc2sys[20675.184]: clockcheck: clock jumped backward or running slower than > expected! > phc2sys[20675.184]: /dev/ptp1 sys offset -502999994984 s0 freq -24351 delay > 2283 > phc2sys[20676.184]: /dev/ptp1 sys offset -502999994973 s0 freq -24351 delay > 2248 > phc2sys[20677.185]: /dev/ptp1 sys offset -502999994944 s0 freq -24351 delay > 2258 > phc2sys[20678.185]: /dev/ptp1 sys offset -502999994990 s1 freq -24331 delay > 2248 > phc2sys[20679.185]: /dev/ptp1 sys offset 72 s2 freq -24287 delay > 2248 > phc2sys[20680.185]: /dev/ptp1 sys offset 33 s2 freq -24295 delay > 2259 > phc2sys[20681.185]: /dev/ptp1 sys offset 29 s2 freq -24263 delay > 2289 > > > Best regards > Georg > This definitely smells like a bug to me. Thanks, Jake _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
