Searched refs:multi (Results 1 – 23 of 23) sorted by relevance
| /tools/testing/selftests/bpf/benchs/ |
| A D | run_bench_trigger.sh | 9 kprobe kprobe-multi \
10 kretprobe kretprobe-multi \
|
| /tools/testing/selftests/bpf/prog_tests/ |
| A D | btf_split.c | 15 static void __test_btf_split(bool multi) in __test_btf_split() argument
67 if (multi) { in __test_btf_split()
80 if (multi) { in __test_btf_split()
|
| /tools/power/cpupower/ |
| A D | cpupower.service.in | 16 WantedBy=multi-user.target
|
| /tools/kvm/kvm_stat/ |
| A D | kvm_stat.service | 17 WantedBy=multi-user.target
|
| /tools/perf/bench/ |
| A D | futex-lock-pi.c | 52 OPT_BOOLEAN( 'M', "multi", ¶ms.multi, "Use multiple futexes"),
143 if (params.multi) { in create_threads()
245 if (params.multi) in bench_futex_lock_pi()
|
| A D | futex.h | 20 bool multi; /* lock-pi */ member
|
| /tools/perf/Documentation/ |
| A D | cpu-and-latency-overheads.txt | 5 these notions are the same. However, for a multi-threaded/multi-process program
6 running on a multi-core machine, these notions are significantly different.
|
| A D | perf-bench.txt | 90 Be multi thread instead of multi process
110 % perf bench sched messaging -t -g 20 # be multi-thread, with 20 groups
|
| /tools/net/ynl/pyynl/ |
| A D | cli.py | 145 if args.multi:
146 ops = [ (item[0], json.loads(item[1]), args.flags or []) for item in args.multi ]
|
| /tools/bpf/bpftool/Documentation/ |
| A D | bpftool-cgroup.rst | 48 | *ATTACH_FLAGS* := { **multi** | **override** }
80 **multi** if a sub-cgroup installs some bpf program, that cgroup program
87 Multiple programs are allowed to be attached to a cgroup with **multi**.
|
| /tools/power/pm-graph/ |
| A D | README | 205 accomplished with sleepgraph's -multi argument. You specify two numbers: the
207 delay in seconds between them. For instance, -multi 20 5: execute 20 tests with
208 a 5 second delay between each, or -multi 24h 0: execute tests over a 24 hour
242 -multi n d
260 Generate or regenerate the summary for a -multi test run. Creates three
277 %> sudo ./sleepgraph.py -m mem -rtcwake 10 -dev -gzip -multi 2000 0
281 %> sudo ./sleepgraph.py -m mem -rtcwake 10 -dev -gzip -multi 2000 0 -skiphtml
|
| /tools/power/pm-graph/config/ |
| A D | example.cfg | 79 # multi: 3 5
|
| /tools/testing/selftests/wireguard/qemu/ |
| A D | Makefile | 341 …)/misc/ss $(IPROUTE2_PATH)/ip/ip $(IPTABLES_PATH)/iptables/xtables-legacy-multi $(NMAP_PATH)/ncat/…
431 $(IPTABLES_PATH)/iptables/xtables-legacy-multi: | $(IPTABLES_PATH)/.installed $(USERSPACE_DEPS)
|
| /tools/power/cpupower/po/ |
| A D | zh_CN.po | 673 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
730 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
750 msgid "System's multi core scheduler setting: "
|
| A D | ka.po | 720 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
781 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
803 msgid "System's multi core scheduler setting: "
|
| A D | fr.po | 679 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
733 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
751 msgid "System's multi core scheduler setting: "
|
| A D | cs.po | 679 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
733 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
751 msgid "System's multi core scheduler setting: "
|
| A D | it.po | 687 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
741 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
760 msgid "System's multi core scheduler setting: "
|
| A D | pt.po | 689 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
743 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
762 msgid "System's multi core scheduler setting: "
|
| A D | de.po | 703 " -m, --sched-mc [VAL] Sets the kernel's multi core scheduler policy.\n"
759 msgid " -m, --sched-mc Gets the kernel's multi core scheduler policy.\n"
781 msgid "System's multi core scheduler setting: "
|
| /tools/bpf/bpftool/bash-completion/ |
| A D | bpftool | 1048 local ATTACH_FLAGS='multi override'
|
| /tools/memory-model/Documentation/ |
| A D | litmus-tests.txt | 917 16-process litmus test. Again, to be fair, the multi-hour run explores
|
| A D | explanation.txt | 612 multi-processor system, the CPUs must share a consistent view of the
|
Completed in 34 milliseconds