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
13   timestamp as struct timespec (nsec resolution).
16   Only for multicast:approximate transmit timestamp obtained by
17   reading the looped packet receive timestamp.
21   multiple timestamp sources, including hardware. Supports generating
30 same is true for all early receive timestamp options.
44 Supports multiple types of timestamp requests. As a result, this
52 The socket option configures timestamp generation for individual
53 sk_buffs (1.3.1), timestamp reporting to the socket's error
65 calls, one to enable timestamp generation and one to disable it.
93   difference between this timestamp and one taken at
97   timestamp taken immediately before send() from this timestamp. On
100   a timestamp is generated at each layer. This allows for fine
108   over-report measurement, because the timestamp is generated when all
118 effect at the timestamp reporting locations in the stack. Timestamps
119 are only reported for packets that also have the relevant timestamp
145   based on timestamp order or payload inspection alone, then.
148   identifier and returns that along with the timestamp. The identifier
159   timestamp is always looped along with a struct sock_extended_err.
161   among all possibly concurrently outstanding timestamp requests for
169   timestamps and on IPv6 packets with transmit timestamp. This option
170   extends them to IPv4 packets with transmit timestamp. One use case
178   timestamp as a cmsg alongside an empty packet, as opposed to
181   the timestamp even if sysctl net.core.tstamp_allow_data is 0.
188   transmit timestamp is available, the stats are available in a
211   each containing just one timestamp.
226 In addition to socket options, timestamp generation can be requested
246 Moreover, applications must still enable timestamp reporting via
264 correlating a timestamp with data is non-trivial. A range of bytes
278 bytestream consistently, if both semantics of the timestamp and the
282 bytestreams, we chose that a timestamp is generated only when all
294 has only one such field, only one timestamp can be generated.
296 In rare cases, a timestamp request can be missed if two requests are
299 send time with the value returned for each timestamp. It can prevent
304 These precautions ensure that the timestamp is generated only when all
305 bytes have passed a timestamp point, assuming that the network stack
342 software timestamp will be generated in the recvmsg() call and passed
343 in ts[0] when a real software timestamp is missing. This happens also
349 socket's error queue with the send timestamp(s) attached. A process
366 type SCM_TSTAMP_* to define the actual timestamp passed in
374 case the timestamp is stored in ts[0].
389 error queue mechanism is just a method to piggyback the timestamp on.
399 block waiting on a timestamp, use poll or select. poll() will return
412 implicitly defined. ts[0] holds a software timestamp if set, ts[1]
413 is again deprecated and ts[2] holds a hardware timestamp if set.