Searched full:becoming (Results 1 – 25 of 34) sorted by relevance
12
111 cpu was just becoming idle113 load did not require balancing when the cpu was just becoming idle115 tasks and failed, when the cpu was just becoming idle117 load_balance() in this domain when the cpu was just becoming idle120 target task was cache-hot when just becoming idle122 find a busier queue while the cpu was just becoming idle124 was just becoming idle but no busier group was found
51 Any updates to a group's bandwidth specification will result in it becoming
20 # they select or depend on end up becoming shared requirements which cannot be29 # CORE_BELL_A then CORE_BELL_A ends up becoming a common BELL feature which
70 risk of becoming isolated if and when hardware FP emulation comes out
99 messages is a prerequisite of becoming a follower. If this
52 prevent the freeze/unfreeze cycle from becoming visible to the tasks
48 mind the filesystem becoming unreadable to future kernels.
58 To avoid this documentation becoming obsolete as the interface evolves, only
181 List of CTI trigger out signals that will be blocked from becoming
120 poll can be used to wait for it becoming empty again. The possible
296 the sector may succeed, and result in the sector becoming readable
28 Other EHCI implementations are becoming available from other vendors;
30 if they are displaced by another ccw device becoming operational on their
165 * "in the process of becoming ready" on open().
170 * 4.13 May 05, 1998 -- Suppress useless "in progress of becoming ready"
245 becoming part of the mainline kernel. The amount of attention that Linus341 staging drivers. So staging is, at best, a stop on the way toward becoming
186 Becoming A Kernel Developer
127 line becoming inactive or the tty layer indicating we want
101 becoming unresponsive, but not causing an immediate crash.
140 they are becoming increasingly aggressive about doing
15 for the device. This is becoming mandatory to simplify the use of advanced
778 becoming unused. (EXT4\_DEFM\_DISCARD)
101 specific (and fake) Ethernet type (later becoming ``skb->protocol``) with the
465 ``OUTPUT`` buffers and any specific timing of buffers becoming
359 ensures that, if A makes a new I/O request slightly after becoming