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
55 Some bits are requests to the stack to try to generate timestamps. Any
58 is possible to selectively request timestamps for a subset of packets
66 Request rx timestamps generated by the network adapter.
69 Request rx timestamps when data enters the kernel. These timestamps
74 Request tx timestamps generated by the network adapter.
77 Request tx timestamps when data leaves the kernel. These timestamps
83 Request tx timestamps prior to entering the packet scheduler. Kernel
96 Request tx timestamps when all data in the send buffer has been
106 The other three bits control which timestamps will be reported in a
113 Report any software timestamps when available.
119 Report hardware timestamps as generated by
132 scheduler. In that case timestamps will be queued onto the error
134 possible to uniquely match timestamps to the original send() calls
148 This option is implemented only for transmit timestamps. There, the
159 timestamps and on IPv6 packets with transmit timestamp. This option
167 Applies to transmit timestamps only. Makes the kernel return the
176 disambiguate timestamps and SOF_TIMESTAMPING_OPT_TSONLY to operate
203 It is essential that all timestamps implement the same semantics,
209 In practice, timestamps can be correlated with segments of a
249 page (`man 7 socket`) describes how timestamps generated with
255 These timestamps are returned in a control message with cmsg_level
262 The structure can return up to three timestamps. This is a legacy
263 feature. Only one field is non-zero at any time. Most timestamps
264 are passed in ts[0]. Hardware timestamps are passed in ts[2].
266 ts[1] used to hold hardware timestamps converted to system time.
272 2.1.1 Transmit timestamps with MSG_ERRQUEUE
274 For transmit timestamps the outgoing packet is looped back to the
276 receives the timestamps by calling recvmsg() with flag MSG_ERRQUEUE
283 timestamps, the ee_errno field is ENOMSG. The other ancillary message
331 2.1.2 Receive timestamps
459 adds the timestamps, therefore the original skb has to be freed now.