Lines Matching full:timestamps

11 The interfaces for receiving network packages timestamps are:
37   Generates timestamps on reception, transmission or both. Supports
39   timestamps for stream sockets.
55 SO_TIMESTAMP_OLD returns incorrect timestamps after the year 2038
61 Its struct timespec allows for higher resolution (ns) timestamps than the
67 SO_TIMESTAMPNS_OLD returns incorrect timestamps after the year 2038
90 Some bits are requests to the stack to try to generate timestamps. Any
93 is possible to selectively request timestamps for a subset of packets
96 Timestamps may also be generated for reasons other than being
101   Request rx timestamps generated by the network adapter.
104   Request rx timestamps when data enters the kernel. These timestamps
109   Request tx timestamps generated by the network adapter. This flag
113   Request tx timestamps when data leaves the kernel. These timestamps
120   Request tx timestamps prior to entering the packet scheduler. Kernel
134   Request tx timestamps when all data in the send buffer has been
146 The other three bits control which timestamps will be reported in a
148 effect at the timestamp reporting locations in the stack. Timestamps
153   Report any software timestamps when available.
159   Report hardware timestamps as generated by
172   scheduler. In that case timestamps will be queued onto the error
174   possible to uniquely match timestamps to the original send() calls
188   This option is implemented only for transmit timestamps. There, the
198   timestamps and on IPv6 packets with transmit timestamp. This option
205   Applies to transmit timestamps only. Makes the kernel return the
213   Optional stats that are obtained along with the transmit timestamps.
219   the transmit timestamps, such as how long a certain block of
224   packets with hardware timestamps. The message contains struct
232   Request both hardware and software timestamps for outgoing packets
234   are enabled at the same time. If both timestamps are generated,
239 disambiguate timestamps and SOF_TIMESTAMPING_OPT_TSONLY to operate
249 1.3.4. Enabling timestamps via control messages
254 Using this feature, applications can sample timestamps per sendmsg()
255 without paying the overhead of enabling and disabling timestamps via
273 setsockopt to receive timestamps::
280 1.4 Bytestream Timestamps
298 It is essential that all timestamps implement the same semantics,
304 In practice, timestamps can be correlated with segments of a
343 Timestamps are read using the ancillary data feature of recvmsg().
345 page (`man 7 socket`) describes how timestamps generated with
352 These timestamps are returned in a control message with cmsg_level
369 SO_TIMESTAMPING_OLD returns incorrect timestamps after the year 2038
372 The structure can return up to three timestamps. This is a legacy
373 feature. At least one field is non-zero at any time. Most timestamps
374 are passed in ts[0]. Hardware timestamps are passed in ts[2].
376 ts[1] used to hold hardware timestamps converted to system time.
386 on hardware transmit timestamps.
388 2.1.1 Transmit timestamps with MSG_ERRQUEUE
391 For transmit timestamps the outgoing packet is looped back to the
393 receives the timestamps by calling recvmsg() with flag MSG_ERRQUEUE
400 timestamps, the ee_errno field is ENOMSG. The other ancillary message
452 2.1.2 Receive timestamps
586   adds the timestamps, therefore the original skb has to be freed now.
629 allow the delivery of multiple hardware timestamps for the same packet, so
650   available, or defer to later. On reception, timestamps might either be
663 performance reasons: timestamps taken as close as possible to the wire have the