Lines Matching refs:packet

7   Generates a timestamp for each incoming packet in (not necessarily
17   reading the looped packet receive timestamp.
70   are generated just after a device driver hands a packet to the
79   prior to, passing the packet to the network interface. Hence, they
83   Request tx timestamps prior to entering the packet scheduler. Kernel
90   machines with virtual devices where a transmitted packet travels
91   through multiple devices and, hence, multiple packet schedulers,
129   Generate a unique identifier along with each packet. A process can
131   can be reordered in the transmit path, for instance in the packet
137   This option associates each packet at send() with a unique
140   sockets, the counter increments with each sent packet. For stream
168   timestamp as a cmsg alongside an empty packet, as opposed to
169   alongside the original packet. This reduces the amount of memory
182 having access to the contents of the original packet, so cannot be
240 possible to construct a packet scheduler configuration that delays
274 For transmit timestamps the outgoing packet is looped back to the
279 outgoing data packet with two ancillary messages attached.
306 explicitly disabling PMTU discovery. If an outgoing packet is fragmented,
314 packet payload that it passed to the stack originally: the socket
319 however, the full packet is queued, taking up budget from SO_RCVBUF.
334 The SCM_TIMESTAMPING ancillary data is sent along with the packet data
379 	 * no outgoing packet will need hardware time stamping;
380 	 * should a packet arrive which asks for it, no hardware
387 	 * the sender of the packet decides which are to be
389 	 * before sending the packet
396 	/* time stamp no incoming packet at all */
399 	/* time stamp any incoming packet */
405 	/* PTP v1, UDP, any kind of event packet */
448 - As soon as the driver has sent the packet and/or obtained a