Re: [PATCH bpf-next] selftests/bpf: Properly enable hwtstamp in xdp_hw_metadata

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 25/01/2023 23.32, Stanislav Fomichev wrote:
The existing timestamping_enable() is a no-op because it applies
to the socket-related path that we are not verifying here
anymore. (but still leaving the code around hoping we can
have xdp->skb path verified here as well)

   poll: 1 (0)
   xsk_ring_cons__peek: 1
   0xf64788: rx_desc[0]->addr=100000000008000 addr=8100 comp_addr=8000
   rx_hash: 3697961069
   rx_timestamp:  1674657672142214773 (sec:1674657672.1422)
   XDP RX-time:   1674657709561774876 (sec:1674657709.5618) delta sec:37.4196
   AF_XDP time:   1674657709561871034 (sec:1674657709.5619) delta sec:0.0001 (96.158 usec)

This output contains some extra output data, which is not part of
current upstream.
I will soon submit an RFC-patch with this extra output to discuss and
figure out what timestamp type we want/expect HW to provide.

   0xf64788: complete idx=8 addr=8000

Also, maybe something to archive here, see [0] for Jesper's note
about NIC vs host clock delta.

0: https://lore.kernel.org/bpf/f3a116dc-1b14-3432-ad20-a36179ef0608@xxxxxxxxxx/


--Jesper




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux