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
60 calls, one to enable timestamp generation and one to disable it.
85   difference between this timestamp and one taken at
89   timestamp taken immediately before send() from this timestamp. On
92   a timestamp is generated at each layer. This allows for fine
99   over-report measurement, because the timestamp is generated when all
108 effect at the timestamp reporting locations in the stack. Timestamps
109 are only reported for packets that also have the relevant timestamp
135   based on timestamp order or payload inspection alone, then.
138   identifier and returns that along with the timestamp. The identifier
149   timestamp is always looped along with a struct sock_extended_err.
151   among all possibly concurrently outstanding timestamp requests for
159   timestamps and on IPv6 packets with transmit timestamp. This option
160   extends them to IPv4 packets with transmit timestamp. One use case
168   timestamp as a cmsg alongside an empty packet, as opposed to
171   the timestamp even if sysctl net.core.tstamp_allow_data is 0.
196 correlating a timestamp with data is non-trivial. A range of bytes
210 bytestream consistently, if both semantics of the timestamp and the
214 bytestreams, we chose that a timestamp is generated only when all
226 has only one such field, only one timestamp can be generated.
228 In rare cases, a timestamp request can be missed if two requests are
231 send time with the value returned for each timestamp. It can prevent
236 These precautions ensure that the timestamp is generated only when all
237 bytes have passed a timestamp point, assuming that the network stack
275 socket's error queue with the send timestamp(s) attached. A process
292 type SCM_TSTAMP_* to define the actual timestamp passed in
300 case the timestamp is stored in ts[0].
315 error queue mechanism is just a method to piggyback the timestamp on.
325 block waiting on a timestamp, use poll or select. poll() will return
338 implicitly defined. ts[0] holds a software timestamp if set, ts[1]
339 is again deprecated and ts[2] holds a hardware timestamp if set.