Searched refs:exhausted (Results 1 – 24 of 24) sorted by relevance
| /Linux-v6.6/drivers/char/xillybus/ |
| D | xillybus_core.c | 700 int empty, reached_eof, exhausted, ready; in xillybus_read() local
765 exhausted = channel->wr_empty; in xillybus_read()
817 if (!exhausted) in xillybus_read()
1210 int full, exhausted; in xillybus_write() local
1299 exhausted = channel->rd_full; in xillybus_write()
1374 if (!exhausted) in xillybus_write()
|
| /Linux-v6.6/arch/xtensa/lib/ |
| D | strnlen_user.S | 95 # exhausted the original len parameter.
|
| /Linux-v6.6/Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 141 If data space is exhausted the pool will either error or queue IO
143 space is exhausted or a metadata operation fails: the pool will error IO
150 that when the pool's metadata space is exhausted the current metadata
|
| D | dm-zoned.rst | 106 be exhausted (all used to map chunks or buffer sequential zones) and
|
| /Linux-v6.6/Documentation/networking/device_drivers/ethernet/microsoft/ |
| D | netvsc.rst | 94 if the buffer is temporarily exhausted, or the packet to be transmitted is
|
| /Linux-v6.6/Documentation/scheduler/ |
| D | sched-domains.rst | 43 chain. While doing that, it checks to see if the current domain has exhausted its
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | sysv-fs.rst | 104 When it is exhausted, new free inodes are found using a linear search.
|
| D | autofs-mount-control.rst | 97 cases (in 2.4) where the available number of mounts are exhausted or
98 where the number of privileged ports available is exhausted.
|
| D | proc.rst | 1656 being exhausted, the allowed memory represents the set of mems assigned to that
1657 cpuset. If it is due to a mempolicy's node(s) being exhausted, the allowed
2161 reason for being scheduled out (time slice exhausted, syscall ...)
|
| D | xfs-delayed-logging-design.rst | 257 exhausted. At this point, we still require a log space reservation to continue
|
| /Linux-v6.6/Documentation/networking/ |
| D | napi.rst | 80 has outstanding work to do (e.g. ``budget`` was exhausted)
|
| /Linux-v6.6/Documentation/admin-guide/mm/ |
| D | concepts.rst | 214 It is possible that on a loaded machine memory will be exhausted and the
|
| D | hugetlbpage.rst | 209 persistent huge page pool is exhausted. As these surplus huge pages become
|
| /Linux-v6.6/Documentation/dev-tools/ |
| D | kfence.rst | 56 The KFENCE memory pool is of fixed size, and if the pool is exhausted, no
|
| /Linux-v6.6/Documentation/admin-guide/sysctl/ |
| D | net.rst | 272 exhausted.
|
| /Linux-v6.6/Documentation/scsi/ |
| D | scsi_eh.rst | 121 will either be retried (if the number of retries is not exhausted)
|
| /Linux-v6.6/Documentation/admin-guide/blockdev/ |
| D | zram.rst | 387 If admins want to allow further write again once the budget is exhausted,
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | xfs.rst | 448 retries and/or timeouts have been exhausted. This will delay unmount
|
| D | cgroup-v2.rst | 2089 The number of tasks in a cgroup can be exhausted in ways which other
|
| /Linux-v6.6/Documentation/gpu/ |
| D | drm-uapi.rst | 216 exhausted.
|
| /Linux-v6.6/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 962 * yet the last S/G was completely exhausted,
|
| D | aic79xx.seq | 1783 * yet the last S/G was completely exhausted,
|
| /Linux-v6.6/arch/arm/ |
| D | Kconfig | 1350 exhausted. The modules will use slightly more memory, but after
|
| /Linux-v6.6/arch/arm64/ |
| D | Kconfig | 2188 the region is exhausted. In this particular case of region
|
