Lines Matching full:packet

14   Generates a timestamp for each incoming packet in (not necessarily
34   reading the looped packet receive timestamp.
105   are generated just after a device driver hands a packet to the
115   prior to, passing the packet to the network interface. Hence, they
120   Request tx timestamps prior to entering the packet scheduler. Kernel
127   machines with virtual devices where a transmitted packet travels
128   through multiple devices and, hence, multiple packet schedulers,
169   Generate a unique identifier along with each packet. A process can
171   can be reordered in the transmit path, for instance in the packet
177   This option associates each packet at send() with a unique
180   sockets, the counter increments with each sent packet. For stream
206   timestamp as a cmsg alongside an empty packet, as opposed to
207   alongside the original packet. This reduces the amount of memory
226   received the packet and its length at layer 2. A valid (non-zero)
245 having access to the contents of the original packet, so cannot be
335 possible to construct a packet scheduler configuration that delays
391 For transmit timestamps the outgoing packet is looped back to the
396 outgoing data packet with two ancillary messages attached.
425 explicitly disabling PMTU discovery. If an outgoing packet is fragmented,
430 2.1.1.4 Packet Payload
434 packet payload that it passed to the stack originally: the socket
439 however, the full packet is queued, taking up budget from SO_RCVBUF.
456 The SCM_TIMESTAMPING ancillary data is sent along with the packet data
511 	    * no outgoing packet will need hardware time stamping;
512 	    * should a packet arrive which asks for it, no hardware
519 	    * the sender of the packet decides which are to be
521 	    * before sending the packet
528 	    /* time stamp no incoming packet at all */
531 	    /* time stamp any incoming packet */
537 	    /* PTP v1, UDP, any kind of event packet */
582 - As soon as the driver has sent the packet and/or obtained a
597 in the data path of a packet. The kernel has no explicit mechanism to allow the
629 allow the delivery of multiple hardware timestamps for the same packet, so
652   ways to the packet), or out-of-band (through another RX timestamping FIFO).
687   responsibility of the PHY driver to send the packet up the stack when the
740    not where the typical issue is.  Transmission proceeds with this packet.