Searched full:busy (Results 1 – 25 of 124) sorted by relevance
12345
| /Documentation/networking/ |
| D | napi.rst | 16 interrupts first (:ref:`busy polling<poll>`).
197 Busy polling
200 Busy polling allows a user process to check for incoming packets before
201 the device interrupt fires. As is the case with any busy polling it trades
202 off CPU cycles for lower latency (production uses of NAPI busy polling
205 Busy polling is enabled by either setting ``SO_BUSY_POLL`` on
207 ``net.core.busy_read`` sysctls. An io_uring API for NAPI busy polling
213 While busy polling is supposed to be used by low latency applications,
221 Such applications can pledge to the kernel that they will perform a busy
225 if ``gro_flush_timeout`` passes without any busy poll call.
[all …]
|
| D | nexthop-group-resilient.rst | 72 keeping the "busy" buckets intact. This way, established flows are ideally
95 be considered "idle". Buckets that are not idle are busy.
153 A second way for the HW to report that a bucket is busy is through the
155 as busy are treated as if traffic hit them.
279 exposes debugfs interface that allows marking individual buckets as busy.
|
| /Documentation/devicetree/bindings/display/ |
| D | repaper.txt | 12 - busy-gpios: BUSY pin
49 busy-gpios = <&gpio 25 0>;
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 81 of idleness (idle, busy, and newly idle):
100 cpu was busy
102 load did not require balancing when busy
104 more tasks and failed, when the cpu was busy
106 sched_balance_rq() in this domain when the cpu was busy
107 13) # of times in this domain pull_task() was called when busy
109 target task was cache-hot when busy
111 find a busier queue while the cpu was busy
113 was busy but no busier group was found
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 22 'armed', 'overflow', and 'busy'.
30 - busy:
31 In the busy state armed devices are in the process of transitioning
63 attribute indicates 'idle', 'armed', or 'busy'. The state transitions
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e17.rst | 52 DS28E17 devices. It is a multiplier used on the calculation of the busy
56 driver checks the DS28E17's busy flag in a loop after the precalculated
60 19-00000002dbd8: busy timeout" in the kernel log.
|
| /Documentation/locking/ |
| D | hwspinlock.rst | 104 msecs). If the hwspinlock is already taken, the function will busy loop
112 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
120 msecs). If the hwspinlock is already taken, the function will busy loop
127 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
136 msecs). If the hwspinlock is already taken, the function will busy loop
144 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
153 msecs). If the hwspinlock is already taken, the function will busy loop
161 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
170 msecs). If the hwspinlock is already taken, the function will busy loop
177 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 62 when the processor is busy-waiting on the value of a variable. The right
63 way to perform a busy wait is::
70 barrier, so, once again, volatile is unnecessary. Of course, busy-
|
| /Documentation/tools/rv/ |
| D | common_ikm.rst | 13 the tool might get busy processing its own events only.
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | adi,ad7091r5.yaml | 59 be attached to ALERT/BUSY/GPO0 pin.
69 # AD7091R-2 does not have ALERT/BUSY/GPO pin
|
| D | adi,ad4695.yaml | 90 - description: Signal coming from the BSY_ALT_GP0 pin (ALERT or BUSY).
92 - description: Signal coming from the GP3 pin (BUSY).
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-w1_ds28e17 | 19 the busy timeout for I2C operations on the connected DS28E17
|
| D | debugfs-hisi-zip | 111 0: busy, 1: idle.
152 with returning busy.
|
| D | debugfs-hisi-sec | 98 0: busy, 1: idle.
138 Description: Dump the total number of requests sent with returning busy.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | raw-nand-chip.yaml | 90 Contains the native Ready/Busy IDs.
97 Ready/Busy pins. Active state refers to the NAND ready state and
|
| D | lpc32xx-mlc.txt | 34 nxp,busy-delay = <10000000>;
|
| D | fsl-upm-nand.txt | 12 - gpios : may specify optional GPIOs connected to the Ready-Not-Busy pins
|
| D | allwinner,sun4i-a10-nand.yaml | 69 Contains the native Ready/Busy IDs.
|
| /Documentation/timers/ |
| D | timers-howto.rst | 23 and will busy wait for enough loop cycles to achieve
45 -- Backed by busy-wait loop:
|
| /Documentation/hwmon/ |
| D | shtc1.rst | 55 the I2C bus will be busy during that time. By default, non-blocking mode
|
| /Documentation/iio/ |
| D | ad7944.rst | 29 CS mode, 3-wire, without busy indicator
49 CS mode, 4-wire, without busy indicator
71 Chain mode, without busy indicator
108 - ``BUSY`` indication
|
| D | ad4000.rst | 65 CS mode, 3-wire, without busy indicator
107 CS mode, 4-wire without busy indicator
|
| /Documentation/userspace-api/gpio/ |
| D | error-codes.rst | 29 - The ioctl can't be handled because the device is busy. Typically
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 34 - The ioctl can't be handled because the device is busy. This is
|
| /Documentation/trace/ |
| D | user_events.rst | 244 Busy: BusyCount
251 Busy: 0
258 Busy: 1
|
12345