Lines Matching +full:software +full:- +full:generated

66 Timestamps may also be generated for reasons other than being
71   Request rx timestamps generated by the network adapter.
75   are generated just after a device driver hands a packet to the
79   Request tx timestamps generated by the network adapter. This flag
84   are generated in the device driver as close as possible, but always
100   a timestamp is generated at each layer. This allows for fine
108   over-report measurement, because the timestamp is generated when all
117 generated control message. Changes to the bits take immediate
123   Report any software timestamps when available.
129   Report hardware timestamps as generated by
149   is derived from a per-socket u32 counter (that wraps). For datagram
200   received the packet and its length at layer 2. A valid (non-zero)
207   Request both hardware and software timestamps for outgoing packets
209   are enabled at the same time. If both timestamps are generated,
235   cmsg->cmsg_level	       = SOL_SOCKET;
236   cmsg->cmsg_type	       = SO_TIMESTAMPING;
237   cmsg->cmsg_len	       = CMSG_LEN(sizeof(__u32));
264 correlating a timestamp with data is non-trivial. A range of bytes
282 bytestreams, we chose that a timestamp is generated only when all
293 relevant sequence number in skb_shinfo(skb)->tskey. Because an skbuff
294 has only one such field, only one timestamp can be generated.
304 These precautions ensure that the timestamp is generated only when all
317 page (`man 7 socket`) describes how timestamps generated with
331 feature. At least one field is non-zero at any time. Most timestamps
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
373 is the first if ts[2] is non-zero, the second otherwise, in which
398 Reading from the error queue is always a non-blocking operation. To
412 implicitly defined. ts[0] holds a software timestamp if set, ts[1]
432 the requested fine-grained filtering for incoming packets is not
457 /* possible values for hwtstamp_config->tx_type */
475 /* possible values for hwtstamp_config->rx_filter */
512 Time stamps for outgoing packets are to be generated as follows:
513 - In hard_start_xmit(), check if (skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP)
514   is set no-zero. If yes, then the driver is expected to do hardware time
516 - If this is possible for the skb and requested, then declare
518   SKBTX_IN_PROGRESS in skb_shinfo(skb)->tx_flags , e.g. with
520       skb_shinfo(skb)->tx_flags |= SKBTX_IN_PROGRESS;
525   software generated time stamps by the network subsystem.
526 - Driver should call skb_tx_timestamp() as close to passing sk_buff to hardware
527   as possible. skb_tx_timestamp() provides a software time stamp if requested
529 - As soon as the driver has sent the packet and/or obtained a
535   should not fall back to software time stamping. The rationale is that
537   software time stamping and therefore could lead to unexpected deltas