Lines Matching refs:timestamps

4 The interfaces for receiving network packages timestamps are:
30   Generates timestamps on reception, transmission or both. Supports
32   timestamps for stream sockets.
47 SO_TIMESTAMP_OLD returns incorrect timestamps after the year 2038
53 Its struct timespec allows for higher resolution (ns) timestamps than the
59 SO_TIMESTAMPNS_OLD returns incorrect timestamps after the year 2038
80 Some bits are requests to the stack to try to generate timestamps. Any
83 is possible to selectively request timestamps for a subset of packets
91   Request rx timestamps generated by the network adapter.
94   Request rx timestamps when data enters the kernel. These timestamps
99   Request tx timestamps generated by the network adapter. This flag
103   Request tx timestamps when data leaves the kernel. These timestamps
111   Request tx timestamps prior to entering the packet scheduler. Kernel
125   Request tx timestamps when all data in the send buffer has been
136 The other three bits control which timestamps will be reported in a
143   Report any software timestamps when available.
149   Report hardware timestamps as generated by
162   scheduler. In that case timestamps will be queued onto the error
164   possible to uniquely match timestamps to the original send() calls
178   This option is implemented only for transmit timestamps. There, the
189   timestamps and on IPv6 packets with transmit timestamp. This option
197   Applies to transmit timestamps only. Makes the kernel return the
206   Optional stats that are obtained along with the transmit timestamps.
212   the transmit timestamps, such as how long a certain block of
218   packets with hardware timestamps. The message contains struct
227   Request both hardware and software timestamps for outgoing packets
229   are enabled at the same time. If both timestamps are generated,
234 disambiguate timestamps and SOF_TIMESTAMPING_OPT_TSONLY to operate
244 1.3.4. Enabling timestamps via control messages
248 Using this feature, applications can sample timestamps per sendmsg()
249 without paying the overhead of enabling and disabling timestamps via
267 setsockopt to receive timestamps:
291 It is essential that all timestamps implement the same semantics,
297 In practice, timestamps can be correlated with segments of a
337 page (`man 7 socket`) describes how timestamps generated with
343 These timestamps are returned in a control message with cmsg_level
360 SO_TIMESTAMPING_OLD returns incorrect timestamps after the year 2038
363 The structure can return up to three timestamps. This is a legacy
364 feature. At least one field is non-zero at any time. Most timestamps
365 are passed in ts[0]. Hardware timestamps are passed in ts[2].
367 ts[1] used to hold hardware timestamps converted to system time.
377 on hardware transmit timestamps.
379 2.1.1 Transmit timestamps with MSG_ERRQUEUE
381 For transmit timestamps the outgoing packet is looped back to the
383 receives the timestamps by calling recvmsg() with flag MSG_ERRQUEUE
390 timestamps, the ee_errno field is ENOMSG. The other ancillary message
438 2.1.2 Receive timestamps
566   adds the timestamps, therefore the original skb has to be freed now.