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