Searched full:blocking (Results 1 – 25 of 725) sorted by relevance
12345678910>>...29
/Linux-v5.10/Documentation/userspace-api/media/dvb/ |
D | ca-fopen.rst | 43 - open in non-blocking mode 44 (blocking mode is the default) 53 significance of blocking or non-blocking mode is described in the 56 blocking mode can later be put into non-blocking mode (and vice versa)
|
D | video-fopen.rst | 54 - O_NONBLOCK open in non-blocking mode 59 - (blocking mode is the default) 68 significance of blocking or non-blocking mode is described in the 71 blocking mode can later be put into non-blocking mode (and vice versa)
|
D | audio-fopen.rst | 54 - O_NONBLOCK open in non-blocking mode 59 - (blocking mode is the default) 67 blocking or non-blocking mode is described in the documentation for 69 of the open() call itself. A device opened in blocking mode can later be 70 put into non-blocking mode (and vice versa) using the F_SETFL command
|
D | dmx-fopen.rst | 46 - open in non-blocking mode 47 (blocking mode is the default) 63 The significance of blocking or non-blocking mode is described in the 66 in blocking mode can later be put into non-blocking mode (and vice versa)
|
D | frontend_f_open.rst | 61 non-blocking or blocking mode was specified. A front-end device opened 62 in blocking mode can later be put into non-blocking mode (and vice
|
D | fe-get-event.rst | 37 not available, the behavior depends on whether the device is in blocking 38 or non-blocking mode. In the latter case, the call fails immediately 58 - There is no event pending, and the device is in non-blocking mode.
|
D | video-get-event.rst | 57 in blocking or non-blocking mode. In the latter case, the call fails 99 - There is no event pending, and the device is in non-blocking mode.
|
/Linux-v5.10/Documentation/hwmon/ |
D | shtc1.rst | 53 1. blocking (pull the I2C clock line down while performing the measurement) or 54 non-blocking mode. Blocking mode will guarantee the fastest result but 55 the I2C bus will be busy during that time. By default, non-blocking mode 57 want to use blocking mode.
|
D | sht3x.rst | 33 1. blocking (pull the I2C clock line down while performing the measurement) or 34 non-blocking mode. Blocking mode will guarantee the fastest result but 35 the I2C bus will be busy during that time. By default, non-blocking mode 37 want to use blocking mode.
|
/Linux-v5.10/fs/btrfs/ |
D | locking.c | 30 * - blocking lock semantics 39 * is done by read-write spinlock and the blocking part is implemented using 45 * blocking semantics - the low-level rwlock is not held but the counter 46 * denotes how many times the blocking lock was held; 91 * Locking pattern - blocking 94 * The blocking write uses the following scheme. The +--+ denotes the spinning 106 * Blocking read is similar. 188 * Mark already held read lock as blocking. Can be nested in write lock by the 194 * The rwlock is released and blocking reader counter is increased. 213 * Mark already held write lock as blocking. [all …]
|
/Linux-v5.10/Documentation/driver-api/ |
D | mailbox.rst | 43 The client might want to operate in blocking mode (synchronously 44 send a message through before returning) or non-blocking/async mode (submit 93 /* Populate non-blocking mode client */ 103 /* Populate blocking mode client */ 106 dc_sync->cl.tx_done = NULL; /* operate in blocking mode */ 123 /* Send message to remote in blocking mode */
|
/Linux-v5.10/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/ |
D | event_fifo_public.h | 22 /*! Blocking read from an event source EVENT[ID] 31 /*! Conditional blocking wait for an event source EVENT[ID] 42 /*! Blocking read from an event source EVENT[ID] 51 /*! Blocking write to an event sink EVENT[ID]
|
D | input_formatter_public.h | 31 /*! Set the blocking mode of INPUT_FORMATTER[ID] 34 \param enable[in] blocking enable flag 40 enabling blocking the inputformatter will wait on the first presented
|
/Linux-v5.10/kernel/ |
D | notifier.c | 54 * @nl: Pointer to head of the blocking notifier chain 100 * @nl: Pointer to head of the blocking notifier chain 226 * Blocking notifier chain routines. All access to the chain is 231 * blocking_notifier_chain_register - Add notifier to a blocking notifier chain 232 * @nh: Pointer to head of the blocking notifier chain 235 * Adds a notifier to a blocking notifier chain. 261 * blocking_notifier_chain_unregister - Remove notifier from a blocking notifier chain 262 * @nh: Pointer to head of the blocking notifier chain 265 * Removes a notifier from a blocking notifier chain. 310 * blocking_notifier_call_chain - Call functions in a blocking notifier chain [all …]
|
/Linux-v5.10/Documentation/driver-api/mmc/ |
D | mmc-async-req.rst | 15 The intention of non-blocking (asynchronous) MMC requests is to minimize the 19 dma_unmap_sg are processing. Using non-blocking MMC requests makes it 26 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking. 48 truly non-blocking. If there is an ongoing async request it waits
|
/Linux-v5.10/arch/m68k/sun3/prom/ |
D | console.c | 16 /* Non blocking get character from console input device, returns -1 31 /* Non blocking put character to console device, returns -1 if 46 /* Blocking version of get character routine above. */ 55 /* Blocking version of put character routine above. */
|
/Linux-v5.10/include/uapi/linux/ |
D | vm_sockets.h | 68 /* Option name for using non-blocking send/receive. Use as the option name 69 * for setsockopt(3) or getsockopt(3) to set or get the non-blocking 71 * send() and recv() can be called in non-blocking contexts for the given 76 * It is not to be confused with conventional non-blocking socket operations.
|
/Linux-v5.10/Documentation/filesystems/ |
D | gfs2-glocks.rst | 13 2. A non-blocking bit lock, GLF_LOCK, which is used to prevent other 164 1. DLM lock time (non-blocking requests) 165 2. DLM lock time (blocking requests) 168 A non-blocking request is one which will complete right 173 "try lock" flag is set. A blocking request covers all the other 226 srtt Smoothed round trip time for non blocking dlm requests 228 srttb Smoothed round trip time for (potentially) blocking dlm requests
|
/Linux-v5.10/drivers/staging/media/atomisp/pci/hive_isp_css_common/host/ |
D | event_fifo_local.h | 41 /* Read from FIFO are blocking, query data availability */ 55 /* Writes to FIFO are blocking, query data space */
|
/Linux-v5.10/kernel/sched/ |
D | completion.c | 271 * try_wait_for_completion - try to decrement a completion without blocking 274 * Return: 0 if a decrement cannot be done without blocking 278 * attempt to decrement the counter without blocking. This 289 * in the non-blocking case, we check x->done in try_wait_for_completion() 291 * return early in the blocking case. in try_wait_for_completion()
|
/Linux-v5.10/Documentation/devicetree/bindings/hwmon/ |
D | sensirion,shtc1.yaml | 31 sensirion,blocking-io: 58 sensirion,blocking-io;
|
/Linux-v5.10/kernel/rcu/ |
D | Kconfig | 58 permits arbitrary sleeping or blocking within RCU read-side critical 196 This option also prevents heavy loads from blocking RCU 210 readers blocking that grace period. Note that any RCU reader 211 blocking an expedited RCU grace period is boosted immediately.
|
/Linux-v5.10/Documentation/block/ |
D | null_blk.rst | 96 blocking=[0/1]: Default: 0 97 Blocking behavior of the request queue. 100 0 Register as a non-blocking blk-mq driver device. 101 1 Register as a blocking blk-mq driver device, null_blk will set
|
/Linux-v5.10/drivers/hwmon/ |
D | shtc1.c | 41 /* delays for non-blocking i2c commands, both in us */ 82 * In blocking mode (clock stretching mode) the I2C bus in shtc1_update_values() 84 * will wait until the data is ready. For non blocking mode, we in shtc1_update_values() 240 data->setup.blocking_io = of_property_read_bool(np, "sensirion,blocking-io"); in shtc1_probe()
|
/Linux-v5.10/drivers/md/persistent-data/ |
D | dm-transaction-manager.h | 27 * The non-blocking version of a transaction manager is intended for use in 29 * You create the non-blocking variant from a normal tm. The interface is 112 * If you're using a non-blocking clone the tm will build up a list of
|
12345678910>>...29