Lines Matching full:timestamp
14 Generates a timestamp for each incoming packet in (not necessarily
15 monotonic) system time. Reports the timestamp via recvmsg() in a
25 timestamp as struct timespec in nsec resolution.
33 Only for multicast:approximate transmit timestamp obtained by
34 reading the looped packet receive timestamp.
38 multiple timestamp sources, including hardware. Supports generating
48 same is true for all early receive timestamp options.
52 Always use SO_TIMESTAMP_NEW timestamp to always get timestamp in
64 Always use SO_TIMESTAMPNS_NEW timestamp to always get timestamp in
73 Supports multiple types of timestamp requests. As a result, this
81 The socket option configures timestamp generation for individual
82 sk_buffs (1.3.1), timestamp reporting to the socket's error
83 queue (1.3.2) and options (1.3.3). Timestamp generation can also
87 1.3.1 Timestamp Generation
95 calls, one to enable timestamp generation and one to disable it.
122 difference between this timestamp and one taken at
126 timestamp taken immediately before send() from this timestamp. On
129 a timestamp is generated at each layer. This allows for fine
137 over-report measurement, because the timestamp is generated when all
143 1.3.2 Timestamp Reporting
148 effect at the timestamp reporting locations in the stack. Timestamps
149 are only reported for packets that also have the relevant timestamp
163 1.3.3 Timestamp Options
175 based on timestamp order or payload inspection alone, then.
178 identifier and returns that along with the timestamp. The identifier
189 timestamp is always looped along with a struct sock_extended_err.
191 among all possibly concurrently outstanding timestamp requests for
198 timestamps and on IPv6 packets with transmit timestamp. This option
199 extends them to IPv4 packets with transmit timestamp. One use case
206 timestamp as a cmsg alongside an empty packet, as opposed to
209 the timestamp even if sysctl net.core.tstamp_allow_data is 0.
215 transmit timestamp is available, the stats are available in a
236 each containing just one timestamp.
252 In addition to socket options, timestamp generation can be requested
272 Moreover, applications must still enable timestamp reporting via
291 correlating a timestamp with data is non-trivial. A range of bytes
305 bytestream consistently, if both semantics of the timestamp and the
309 bytestreams, we chose that a timestamp is generated only when all
321 has only one such field, only one timestamp can be generated.
323 In rare cases, a timestamp request can be missed if two requests are
326 send time with the value returned for each timestamp. It can prevent
331 These precautions ensure that the timestamp is generated only when all
332 bytes have passed a timestamp point, assuming that the network stack
366 Always use SO_TIMESTAMPING_NEW timestamp to always get timestamp in
384 software timestamp will be generated in the recvmsg() call and passed
385 in ts[0] when a real software timestamp is missing. This happens also
392 socket's error queue with the send timestamp(s) attached. A process
405 2.1.1.2 Timestamp types
410 type SCM_TSTAMP_* to define the actual timestamp passed in
418 case the timestamp is stored in ts[0].
435 error queue mechanism is just a method to piggyback the timestamp on.
446 block waiting on a timestamp, use poll or select. poll() will return
460 implicitly defined. ts[0] holds a software timestamp if set, ts[1]
461 is again deprecated and ts[2] holds a hardware timestamp if set.
639 have a PTP TX timestamp register (or sometimes a FIFO) where the timestamp
640 becomes available. There may be an IRQ that is raised upon this timestamp's
644 later use (when the timestamp becomes available). Each skb is annotated with
649 to the driver, for it to annotate it with a timestamp, if that is immediately
653 Deferral on RX is typically necessary when retrieving the timestamp needs a
662 switches do. However, PHYs may be able to detect and timestamp PTP packets, for
688 timestamp is available.
729 timestamp.
735 current skb requires a TX timestamp ("``skb_shinfo(skb)->tx_flags &
743 is necessary to collect any TX timestamp for it. Here is where the typical
755 this enhanced check will avoid delivering a duplicated TX timestamp to user