Lines Matching refs:frame

144 As capture, each frame contains two parts:
148 |                    | of this frame
180  frame base + TPACKET_HDRLEN - sizeof(struct sockaddr_ll)
184  frame base + TPACKET_ALIGN(sizeof(struct tpacket_hdr))
187 the frame (for payload alignment with SOCK_RAW mode for instance) you
210         unsigned int    tp_frame_size;  /* Size of frame */
240 | frame 1 | frame 2 |    | frame 3 | frame 4 |    
245 | frame 5 | frame 6 |    | frame 7 | frame 8 |
248 A frame can be of any size with the only condition it can fit in a block. A block
249 can only hold an integer number of frames, or in other words, a frame cannot 
332 <frame size>  : it's an upper bound of frame's capture size (more on this later)
345 	<block number> * <block size> / <frame size>
355 and a value for <frame size> of 2048 bytes. These parameters will yield
375 If you check the source code you will see that what I draw here as a frame
376 is not only the link level frame. At the beginning of each frame there is a 
377 header called struct tpacket_hdr used in PACKET_MMAP to hold link level's frame
378 meta information like timestamp. So what we draw here a frame it's really 
419 the frames. This is because a frame cannot be spawn across two
435 At the beginning of each frame there is an status field (see 
436 struct tpacket_hdr). If this field is 0 means that the frame is ready
437 to be used for the kernel, If not, there is a frame the user can read 
448 TP_STATUS_COPY        : This flag indicates that the frame (and associated
485 can use again that frame buffer.
511 packet, the user fills a data buffer of an available frame, sets tp_len to
569 		1. Blocks can be configured with non-static frame-size
740 AF_PACKET's TPACKET_V3 ring buffer can be configured to use non-static frame
749  *) Non static frame size to capture entire packet payload
1038 frames to be updated resp. the frame handed over to the application, iv) walk
1044 in a first step to see if the frame belongs to the application, and then