Lines Matching refs:timestamp

7   Generates a timestamp for each incoming packet in (not necessarily
8   monotonic) system time. Reports the timestamp via recvmsg() in a
18   timestamp as struct timespec in nsec resolution.
26   Only for multicast:approximate transmit timestamp obtained by
27   reading the looped packet receive timestamp.
31   multiple timestamp sources, including hardware. Supports generating
40 same is true for all early receive timestamp options.
44 Always use SO_TIMESTAMP_NEW timestamp to always get timestamp in
56 Always use SO_TIMESTAMPNS_NEW timestamp to always get timestamp in
64 Supports multiple types of timestamp requests. As a result, this
72 The socket option configures timestamp generation for individual
73 sk_buffs (1.3.1), timestamp reporting to the socket's error
85 calls, one to enable timestamp generation and one to disable it.
113   difference between this timestamp and one taken at
117   timestamp taken immediately before send() from this timestamp. On
120   a timestamp is generated at each layer. This allows for fine
128   over-report measurement, because the timestamp is generated when all
138 effect at the timestamp reporting locations in the stack. Timestamps
139 are only reported for packets that also have the relevant timestamp
165   based on timestamp order or payload inspection alone, then.
168   identifier and returns that along with the timestamp. The identifier
179   timestamp is always looped along with a struct sock_extended_err.
181   among all possibly concurrently outstanding timestamp requests for
189   timestamps and on IPv6 packets with transmit timestamp. This option
190   extends them to IPv4 packets with transmit timestamp. One use case
198   timestamp as a cmsg alongside an empty packet, as opposed to
201   the timestamp even if sysctl net.core.tstamp_allow_data is 0.
208   transmit timestamp is available, the stats are available in a
231   each containing just one timestamp.
246 In addition to socket options, timestamp generation can be requested
266 Moreover, applications must still enable timestamp reporting via
284 correlating a timestamp with data is non-trivial. A range of bytes
298 bytestream consistently, if both semantics of the timestamp and the
302 bytestreams, we chose that a timestamp is generated only when all
314 has only one such field, only one timestamp can be generated.
316 In rare cases, a timestamp request can be missed if two requests are
319 send time with the value returned for each timestamp. It can prevent
324 These precautions ensure that the timestamp is generated only when all
325 bytes have passed a timestamp point, assuming that the network stack
357 Always use SO_TIMESTAMPING_NEW timestamp to always get timestamp in
375 software timestamp will be generated in the recvmsg() call and passed
376 in ts[0] when a real software timestamp is missing. This happens also
382 socket's error queue with the send timestamp(s) attached. A process
399 type SCM_TSTAMP_* to define the actual timestamp passed in
407 case the timestamp is stored in ts[0].
422 error queue mechanism is just a method to piggyback the timestamp on.
432 block waiting on a timestamp, use poll or select. poll() will return
445 implicitly defined. ts[0] holds a software timestamp if set, ts[1]
446 is again deprecated and ts[2] holds a hardware timestamp if set.