Searched refs:ran (Results 1 – 25 of 27) sorted by relevance
12
19 local_node A process ran on this node and got memory from it.21 other_node A process ran on this node and got memory from another node.
9 pointed out that (ALSA) ISA drivers ran into the problem of not having
744 When the code disables itself at runtime this is most likely because it ran
838 u64 ran; in nvmet_fc_alloc_target_assoc() local860 get_random_bytes(&ran, sizeof(ran) - BYTES_FOR_QID); in nvmet_fc_alloc_target_assoc()861 ran = ran << BYTES_FOR_QID_SHIFT; in nvmet_fc_alloc_target_assoc()866 if (ran == tmpassoc->association_id) { in nvmet_fc_alloc_target_assoc()871 assoc->association_id = ran; in nvmet_fc_alloc_target_assoc()
61 4) Check that ``.exe`` binaries can be ran without the need of a
44 streams, or the xHCI driver ran out of memory), or the number of streams the
152 the hrtimer implementation details in praxis, and we also ran the posix153 timer tests in order to ensure specification compliance. We also ran
41 ran and how often it should be expected to run. It can also258 since the grace-period kthread ran. The "jiffies_till_next_fqs"277 kthread last ran on CPU 5.
246 o "nt": The number of times rcutorture ran RCU read-side code from
24 I have a RadioTrack card from back when I ran an MS-Windows platform. After
278 Indicates whether current channel ran out of buffers.
314 Indicates whether current channel ran out of buffers.
136 last ran on a different cpu in this domain
187 request to the target because it ran out of credits. For more
88 - cpu: cpu number the task ran at the time of sample89 - socket: processor socket number the task ran at the time of sample
360 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */423 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
982 0x1 Command ran and succeeded983 … 0x2 Command ran and failed (partial results may be been985 … 0x3 Command ran and was killed (partial execution may
28 the linux-kernel mailing list, where it immediately ran into problems.
1066 runned||ran
152 a while later i ran across the great crypt(3) package mentioned above.
57 This function may return -ENOMEM if it ran out of memory or -EEXIST if the tag
707 1. Why not "volume" for instance? "volume" ran the risk of confusing
99 printing out interesting data such as what you would see if you ran
5035 u64 ran = se->sum_exec_runtime - se->prev_sum_exec_runtime; in hrtick_start_fair() local5036 s64 delta = slice - ran; in hrtick_start_fair()
1037 and it may look like only one CPU ran (the one with the1769 ran.
