Lines Matching refs:timestamps

4 The interfaces for receiving network packages timestamps are:
20   Generates timestamps on reception, transmission or both. Supports
22   timestamps for stream sockets.
38 Its struct timespec allows for higher resolution (ns) timestamps than the
60 Some bits are requests to the stack to try to generate timestamps. Any
63 is possible to selectively request timestamps for a subset of packets
71   Request rx timestamps generated by the network adapter.
74   Request rx timestamps when data enters the kernel. These timestamps
79   Request tx timestamps generated by the network adapter. This flag
83   Request tx timestamps when data leaves the kernel. These timestamps
91   Request tx timestamps prior to entering the packet scheduler. Kernel
105   Request tx timestamps when all data in the send buffer has been
116 The other three bits control which timestamps will be reported in a
123   Report any software timestamps when available.
129   Report hardware timestamps as generated by
142   scheduler. In that case timestamps will be queued onto the error
144   possible to uniquely match timestamps to the original send() calls
158   This option is implemented only for transmit timestamps. There, the
169   timestamps and on IPv6 packets with transmit timestamp. This option
177   Applies to transmit timestamps only. Makes the kernel return the
186   Optional stats that are obtained along with the transmit timestamps.
192   the transmit timestamps, such as how long a certain block of
198   packets with hardware timestamps. The message contains struct
207   Request both hardware and software timestamps for outgoing packets
209   are enabled at the same time. If both timestamps are generated,
214 disambiguate timestamps and SOF_TIMESTAMPING_OPT_TSONLY to operate
224 1.3.4. Enabling timestamps via control messages
228 Using this feature, applications can sample timestamps per sendmsg()
229 without paying the overhead of enabling and disabling timestamps via
247 setsockopt to receive timestamps:
271 It is essential that all timestamps implement the same semantics,
277 In practice, timestamps can be correlated with segments of a
317 page (`man 7 socket`) describes how timestamps generated with
323 These timestamps are returned in a control message with cmsg_level
330 The structure can return up to three timestamps. This is a legacy
331 feature. At least one field is non-zero at any time. Most timestamps
332 are passed in ts[0]. Hardware timestamps are passed in ts[2].
334 ts[1] used to hold hardware timestamps converted to system time.
344 on hardware transmit timestamps.
346 2.1.1 Transmit timestamps with MSG_ERRQUEUE
348 For transmit timestamps the outgoing packet is looped back to the
350 receives the timestamps by calling recvmsg() with flag MSG_ERRQUEUE
357 timestamps, the ee_errno field is ENOMSG. The other ancillary message
405 2.1.2 Receive timestamps
533   adds the timestamps, therefore the original skb has to be freed now.