Lines Matching full:hardware
30 to receive data from the hardware. A "full" descriptor has data in it,
38 ring is handed off to the hardware, which sequentially fills in the
43 and "tail" pointers, managed by the OS, and a hardware current
45 currently being filled. When this descr is filled, the hardware
48 and everything in front of it should be "empty". If the hardware
52 The tail pointer tails or trails the hardware pointer. When the
53 hardware is ahead, the tail pointer will be pointing at a "full"
58 flowing, then the tail pointer can catch up to the hardware pointer.
66 dma-mapping it so as to make it visible to the hardware. The OS will
93 In the above, the hardware has filled in one descr, number 20. Both
117 the hardware can fill them, there is no problem. If, for some reason,
118 the OS fails to empty the RX ring fast enough, the hardware GDACTDPA
129 In particular, it will clear the descriptor on which the hardware had
130 stopped. However, once the hardware has decided that a certain
135 this descr to be filled. However, the hardware has skipped this descr,
138 while the hardware is waiting for a different set of descrs to become
164 Since its already full, the hardware can do nothing more, and thus has
169 to do, and the hardware has nowhere to put incoming data.
174 the hardware has skipped a descr or two (sometimes dozens under heavy
193 in the ring. The hardware can empty the ring about four times per jiffy,
201 interrupts, as the hardware can empty the queue faster than the kernel