Lines Matching refs:OS
31 and is waiting to be emptied and processed by the OS. A "not-in-use"
35 During normal operation, on device startup, the OS (specifically, the
39 buffers, and marks them "full". The OS follows up, taking the full
43 and "tail" pointers, managed by the OS, and a hardware current
54 descr. The OS will process this descr, and then mark it "not-in-use",
59 The OS will then note that the current tail is "empty", and halt
64 a "not-in-use" descr. The OS will perform various housekeeping duties
66 dma-mapping it so as to make it visible to the hardware. The OS will
71 pointer, at which point the OS will notice that the head descr is
116 As long as the OS can empty out the RX buffers at a rate faster than
118 the OS fails to empty the RX ring fast enough, the hardware GDACTDPA
128 When the OS finally has a chance to run, it will empty out the RX ring.
134 which, from the OS point of view, is empty; the OS will be waiting for
136 and is filling the next descrs. Since the OS doesn't see this, there
137 is a potential deadlock, with the OS waiting for one descr to fill,
157 marked xa... which is "empty". Thus, from the OS point of view, there
160 as explained in the last section. The OS is waiting for descr 255 to
168 and there can be no forward progress; the OS thinks there's nothing