Searched refs:exhausted (Results 1 – 16 of 16) sorted by relevance
700 int empty, reached_eof, exhausted, ready; in xillybus_read() local765 exhausted = channel->wr_empty; in xillybus_read()817 if (!exhausted) in xillybus_read()1209 int full, exhausted; in xillybus_write() local1298 exhausted = channel->rd_full; in xillybus_write()1373 if (!exhausted) in xillybus_write()
51 memory is exhausted.
95 # exhausted the original len parameter.
141 If data space is exhausted the pool will either error or queue IO143 space is exhausted or a metadata operation fails: the pool will error IO150 that when the pool's metadata space is exhausted the current metadata
106 be exhausted (all used to map chunks or buffer sequential zones) and
94 if the buffer is temporarily exhausted, or the packet to be transmitted is
97 cases (in 2.4) where the available number of mounts are exhausted or98 where the number of privileged ports available is exhausted.
214 It is possible that on a loaded machine memory will be exhausted and the
121 will either be retried (if the number of retries is not exhausted)
291 exhausted.
420 If admins want to allow further write again once the budget is exhausted,
962 * yet the last S/G was completely exhausted,
1783 * yet the last S/G was completely exhausted,
1273 exhausted. The modules will use slightly more memory, but after
2331 the region is exhausted. In this particular case of region
2386 The number of tasks in a cgroup can be exhausted in ways which other