Searched refs:blocked (Results 1 – 25 of 26) sorted by relevance
12
| /Documentation/ |
| D | rt-mutex-design.txt | 80 blocked on one of its locks. This is described in more detail
95 waiter - A waiter is a struct that is stored on the stack of a blocked
97 a process being blocked on the mutex, it is fine to allocate
100 the task is blocked on. It also has the plist node structures to
107 waiters - A list of processes that are blocked on a mutex.
123 would never diverge, since a process can't be blocked on more than one
132 B blocked on L1
134 C blocked on L2
136 D blocked on L3
138 E blocked on L4
[all …]
|
| D | md.txt | 271 clean, but writes are blocked waiting for 'active' to be written.
300 blocked - device has failed, metadata is "external",
303 it were not faulty are blocked.
313 Writing "blocked" sets the "blocked" flag.
314 Writing "-blocked" clear the "blocked" flag and allows writes
318 or 'blocked' causes an event.
465 within the array where IO will be blocked. This is currently
|
| D | rfkill.txt | 21 made to not emit any energy when "blocked". rfkill is not about blocking data
115 wireless transmitter is to be *blocked* from operating.
202 are locked in the blocked state (rfkill will refuse to unblock them).
205 and either do nothing (leave transmitters blocked, but now unlocked),
248 3. The transmitter can be made to not emit any energy when "blocked":
281 causes wireless transmitters to be blocked regardless of the kernel's will, it
364 energy, it is not blocked in rfkill terms.
416 If either one of these rfkill lines are active, the transmitter is blocked by
|
| D | rt-mutex.txt | 21 boosting to the owner of the other rt_mutex it gets blocked on. The
|
| D | sysrq.txt | 112 'w' - Dumps tasks that are in uninterruptable (blocked) state.
|
| D | parport-lowlevel.txt | 563 the caller still owns the port and the call blocked.
|
| /Documentation/accounting/ |
| D | cgroupstats.txt | 18 about tasks blocked on I/O. If CONFIG_TASK_DELAY_ACCT is disabled, this
25 sleeping 1, blocked 0, running 1, stopped 0, uninterruptible 0
27 sleeping 155, blocked 0, running 1, stopped 0, uninterruptible 2
|
| /Documentation/filesystems/ |
| D | directory-locking | 56 renames will be blocked on filesystem lock and we don't start changing
63 Now consider the minimal deadlock. Each process is blocked on
66 not contended, since any process blocked on it is not holding any locks.
67 Thus all processes are blocked on ->i_mutex.
70 creation can't be a part of deadlock - it can't be blocked on source
76 is blocked on belongs to child of that object due to (1).
|
| D | dnotify.txt | 36 is often blocked, so it is better to use (at least) SIGRTMIN + 1.
|
| D | proc.txt | 233 blocked bitmap of blocked signals (obsolete)
925 The "procs_blocked" line gives the number of processes currently blocked,
|
| D | coda.txt | 299 the calling thread in P is blocked in upcall. A pointer in the
1655 explicitly blocked.
|
| /Documentation/ia64/ |
| D | mca.txt | 64 running or not. That is, whether it is on a cpu or is blocked. The
67 INIT event are no longer running, they have been converted to blocked
154 does not bother making the user space process look like a blocked task,
171 exactly like any other blocked task, i.e. it now appears to be
180 If the previous task has been verified and converted to a blocked
|
| /Documentation/cgroups/ |
| D | freezer-subsystem.txt | 22 blocked, or ignored it can be seen by waiting or ptracing parent tasks.
101 3) The tasks that blocked the cgroup from entering the "FROZEN"
|
| /Documentation/lguest/ |
| D | lguest.c | 174 bool blocked; member
861 vq->blocked = true; in block_vq()
1064 if (!vq->blocked) in handle_timeout()
1068 vq->blocked = false; in handle_timeout()
1178 vq->blocked = false; in add_virtqueue()
|
| /Documentation/arm/Sharp-LH/ |
| D | CompactFlash | 23 explicitly blocked by the OUTB function--not pretty, but effective.
|
| /Documentation/isdn/ |
| D | README.audio | 17 larger values is blocked.
|
| /Documentation/PCI/ |
| D | pci-error-recovery.txt | 86 pci_channel_io_frozen, /* I/O to channel is blocked */
115 is isolated, in that all I/O is blocked: all reads return 0xffffffff,
200 >>> such an error might cause IOs to be re-blocked for the whole
|
| /Documentation/RCU/ |
| D | whatisRCU.txt | 870 (thus read-holding rcu_gp_mutex), task B blocked
872 task C blocked in rcu_read_lock() attempting to
879 cannot be blocked by tasks executing synchronize_rcu().
|
| /Documentation/power/ |
| D | freezing-of-tasks.txt | 148 and B is frozen in the meantime, then A will be blocked until B is thawed, which
|
| /Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 150 3. SYNCHRONIZE_CACHE is not supported by FW and thus blocked by driver.
|
| D | scsi_eh.txt | 179 (*QUESTION* why is it needed? All operations will be blocked
|
| D | ChangeLog.lpfc | 356 the small window while the device was blocked to be errored w/
565 * Have rmmod path cleanup blocked devices before scsi_remove_host.
644 * Added a blocked member to the lpfc_target structure for
|
| /Documentation/development-process/ |
| D | 6.Followthrough | 90 be hopelessly blocked. Appealing to Andrew should not be done lightly,
|
| /Documentation/sound/alsa/ |
| D | ALSA-Configuration.txt | 85 opening a busy OSS PCM device won't be blocked but return
|
| /Documentation/s390/ |
| D | Debugging390.txt | 882 saveset = current->blocked;
|
12