Searched refs:ran (Results 1 – 25 of 40) sorted by relevance
12
| /Linux-v5.15/Documentation/admin-guide/ |
| D | numastat.rst | 34 local_node A process ran on this node's CPU,
37 other_node A process ran on a different node's CPU
|
| D | mono.rst | 61 4) Check that ``.exe`` binaries can be ran without the need of a
|
| /Linux-v5.15/tools/memory-model/scripts/ |
| D | README | 48 judge whether the test ran correctly. Not normally run manually,
|
| /Linux-v5.15/drivers/nvme/target/ |
| D | fc.c | 1110 u64 ran; in nvmet_fc_alloc_target_assoc() local
1137 get_random_bytes(&ran, sizeof(ran) - BYTES_FOR_QID); in nvmet_fc_alloc_target_assoc()
1138 ran = ran << BYTES_FOR_QID_SHIFT; in nvmet_fc_alloc_target_assoc()
1143 if (ran == tmpassoc->association_id) { in nvmet_fc_alloc_target_assoc()
1149 assoc->association_id = ran; in nvmet_fc_alloc_target_assoc()
|
| /Linux-v5.15/Documentation/RCU/ |
| D | stallwarn.rst | 43 ran and how often it should be expected to run. It can also
278 since the grace-period kthread ran. The "jiffies_till_next_fqs"
298 kthread last ran on CPU 5.
313 Here "cpu" indicates that the grace-period kthread last ran on CPU 4,
|
| D | torture.rst | 87 * "nt": The number of times rcutorture ran RCU read-side code from
244 "TREE04"). If a given scenario ran more than once (as in "--configs
250 If the test ran in a git repository, then this file contains the commit
|
| /Linux-v5.15/Documentation/driver-api/usb/ |
| D | bulk-streams.rst | 44 streams, or the xHCI driver ran out of memory), or the number of streams the
|
| /Linux-v5.15/Documentation/timers/ |
| D | hrtimers.rst | 152 the hrtimer implementation details in praxis, and we also ran the posix
153 timer tests in order to ensure specification compliance. We also ran
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-stratix10-rsu | 113 2 both first and second stage bootloader ran
|
| D | sysfs-bus-most | 282 Indicates whether channel ran out of buffers.
|
| /Linux-v5.15/Documentation/dev-tools/kunit/ |
| D | index.rst | 85 someone sends you some code. Why trust that someone ran all their tests
|
| D | running_tips.rst | 162 Then we'd see output like this in dmesg signaling the test ran and passed:
|
| /Linux-v5.15/Documentation/driver-api/media/drivers/ |
| D | radiotrack.rst | 26 I have a RadioTrack card from back when I ran an MS-Windows platform. After
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | isa.rst | 9 pointed out that (ALSA) ISA drivers ran into the problem of not having
|
| /Linux-v5.15/Documentation/scheduler/ |
| D | sched-stats.rst | 147 last ran on a different cpu in this domain
|
| D | sched-energy.rst | 138 save energy compared to leaving it on prev_cpu, i.e. the CPU where the task ran
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-driver-ib_srp | 190 request to the target because it ran out of credits. For more
|
| /Linux-v5.15/drivers/staging/most/Documentation/ABI/ |
| D | sysfs-class-most.txt | 314 Indicates whether current channel ran out of buffers.
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | glossary.txt | 168 store after earlier memory references that ran on that same CPU.
|
| /Linux-v5.15/drivers/mtd/nand/raw/ |
| D | meson_nand.c | 59 #define CMDRWGEN(cmd_dir, ran, bch, short_mode, page_size, pages) \ argument
62 ((ran) << 19) | \
|
| /Linux-v5.15/Documentation/sparc/oradax/ |
| D | oracle-dax.rst | 367 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
433 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
|
| D | dax-hv-api.txt | 982 0x1 Command ran and succeeded
983 … 0x2 Command ran and failed (partial results may be been
985 … 0x3 Command ran and was killed (partial execution may
|
| /Linux-v5.15/tools/perf/Documentation/ |
| D | perf-report.txt | 88 - cpu: cpu number the task ran at the time of sample
89 - socket: processor socket number the task ran at the time of sample
|
| /Linux-v5.15/Documentation/process/ |
| D | 3.Early-stage.rst | 28 the linux-kernel mailing list, where it immediately ran into problems.
|
| /Linux-v5.15/Documentation/crypto/ |
| D | descore-readme.rst | 187 a while later i ran across the great crypt(3) package mentioned above.
|
12
