Lines Matching refs:frames

142 know the header size of frames used in the circular buffer.
211         unsigned int    tp_frame_nr;    /* Total number of frames */
216 Being mapped in the capture process allows reading the captured frames and 
220 region of memory and holds tp_block_size/tp_frame_size frames. The total number 
249 can only hold an integer number of frames, or in other words, a frame cannot 
259 the PACKET_MMAP buffer could hold only 32768 frames in a 32 bit architecture or
343 and, the number of frames be
361 262144 MiB / 2048 bytes = 134217728 frames
416 If tp_frame_size is a divisor of tp_block_size frames will be 
418 tp_block_size/tp_frame_size frames there will be a gap between 
419 the frames. This is because a frame cannot be spawn across two
457                         The number of frames that can be buffered to
481 The kernel initializes all frames to TP_STATUS_KERNEL, when the kernel
500 then poll for frames.
510 First, the kernel initializes all frames to TP_STATUS_AVAILABLE. To send a
513 This can be done on multiple frames. Once the user is ready to transmit, it
516 frames with TP_STATUS_SENDING until the end of transfer.
1036 Getting timestamps for the TX_RING works as follows: i) fill the ring frames,
1038 frames to be updated resp. the frame handed over to the application, iv) walk
1039 through the frames to pick up the individual hw/sw timestamps.