| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cgroups.rst | 51 or more subsystems.
62 hierarchy, and a set of subsystems; each subsystem has system-specific
76 tracking. The intention is that other subsystems hook into the generic
98 specific subsystems such as cpusets to provide additional behaviour as
103 different subsystems - having parallel hierarchies allows each
106 unrelated subsystems needed to be forced into the same tree of
110 separate hierarchy; at the other extreme, all subsystems
143 (by putting those resource subsystems in different hierarchies),
209 comma-separated list of subsystems to mount as the filesystem mount
211 mount a hierarchy containing all registered subsystems.
[all …]
|
| H A D | memcg_test.rst | 233 9.6 Mount with other subsystems
236 Mounting with other subsystems is a good test because there is a
237 race and lock dependency with other cgroup subsystems.
|
| /linux/drivers/soc/qcom/ |
| H A D | qcom_stats.c | 49 static const struct subsystem_data subsystems[] = { variable
298 for (i = 0; i < ARRAY_SIZE(subsystems); i++) in qcom_create_subsystem_stat_files()
299 debugfs_create_file(subsystems[i].name, 0400, root, (void *)&subsystems[i], in qcom_create_subsystem_stat_files()
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | style.rst | 23 To make tests easy to find, they are grouped into suites and subsystems. A test
38 Test subsystems should be named after the code being tested, either after the
40 subsystems should be named to avoid ambiguity where necessary.
45 example, subsystems could be called:
71 The KUnit API and tools do not explicitly know about subsystems. They are
81 shutdown code which is run for all tests in the suite. Not all subsystems need
|
| /linux/Documentation/admin-guide/ |
| H A D | workload-tracing.rst | 4 Discovering Linux kernel subsystems used by a workload
102 subsystems used by these workloads. Let's start with an overview of these
110 benchmarks for executing different subsystems in the Linux kernel and
114 integrate transparently, and use performance-rich tooling subsystems.
120 you to exercise various physical subsystems of the computer, as well as
189 This way we can find the kernel subsystems used by a process when it is
240 benchmarks for executing different subsystems in the Linux kernel and
258 the kernel. It allows you to exercise various physical subsystems of the
600 … by OpenAPS <https://elisa.tech/blog/2022/02/02/discovery-linux-kernel-subsystems-used-by-openaps>…
601 …* `ELISA-White-Papers-Discovering Linux kernel subsystems used by a workload <https://github.com/e…
|
| H A D | lockup-watchdogs.rst | 37 perf subsystems, respectively. A direct consequence of this is that,
39 subsystems are present.
|
| /linux/Documentation/devicetree/bindings/arm/omap/ |
| H A D | crossbar.txt | 2 the needs of its many peripherals and subsystems. All of the
3 interrupt lines from the subsystems are not needed at the same
|
| /linux/drivers/clk/baikal-t1/ |
| H A D | Kconfig | 8 responsible for the chip subsystems clocking and resetting. It
48 AXI-bus and some subsystems reset. These are mainly the
|
| /linux/drivers/dma/ |
| H A D | TODO | 11 4. Check other subsystems for dma drivers and merge/move to dmaengine
|
| /linux/Documentation/userspace-api/ebpf/ |
| H A D | index.rst | 9 kernel subsystems, including networking, tracing and Linux security modules
|
| /linux/drivers/nvme/target/ |
| H A D | discovery.c | 76 list_for_each_entry(s, &port->subsystems, entry) { in nvmet_subsys_disc_changed()
151 list_for_each_entry(p, &req->port->subsystems, entry) { in discovery_log_entries()
216 list_for_each_entry(p, &req->port->subsystems, entry) { in nvmet_execute_disc_get_log_page()
|
| /linux/Documentation/driver-api/80211/ |
| H A D | introduction.rst | 9 These books attempt to give a description of the various subsystems
|
| /linux/Documentation/driver-api/pm/ |
| H A D | notifiers.rst | 13 There are some operations that subsystems or drivers may want to carry out
15 to be fully functional, so the drivers' and subsystems' ``->suspend()`` and
|
| /linux/Documentation/devicetree/bindings/powerpc/ |
| H A D | ibm,vas.txt | 3 VAS is a hardware mechanism that allows kernel subsystems and user processes
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | vexpress-scc.txt | 10 (like silicon temperature sensors) and as interface to other subsystems
|
| /linux/fs/sysfs/ |
| H A D | Kconfig | 14 and other kernel subsystems.
|
| /linux/Documentation/driver-api/iio/ |
| H A D | intro.rst | 11 :doc:`input <../input>` subsystems. Hwmon is directed at low sample rate
|
| /linux/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 10 subsystems. Modern systems require extensive integration between all three
11 classes; this document details how applications and kernel subsystems should
16 support, however any other subsystems should also follow this design and advice.
277 are not portable between contexts, processes, devices, or subsystems.
283 contexts, processes, devices, and subsystems.
304 The concept of modifiers post-dates all of the subsystems mentioned above. As
381 Any new users - userspace programs and protocols, kernel subsystems, etc -
|
| /linux/Documentation/driver-api/ |
| H A D | ioctl.rst | 55 Some subsystems use version numbers in data structures to overload
75 -ENOTTY being returned from the system call. Some subsystems return
80 commands. As all subsystems are now responsible for handling compat
213 subsystems implement the same command for multiple drivers. Ideally the
|
| /linux/Documentation/pcmcia/ |
| H A D | locking.rst | 6 and PCMCIA subsystems.
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | intro.rst | 79 of IDs to subsystems and provided little supporting infrastructure.
86 subsystems (and subsystem ID allocation), introspection and simplifies
90 number of subsystems using Generic Netlink outnumbers the older
94 the Linux kernel (or another of the 20 subsystems using Classic
129 multiple subsystems in a single protocol so it uses this field to
167 versioning of the APIs provided by the subsystems. No subsystem to
556 Netlink refers to subsystems as families. This is a remnant of using
|
| /linux/Documentation/timers/ |
| H A D | hrtimers.rst | 8 (kernel/timers.c), why do we need two timer subsystems? After a lot of
60 users like drivers and subsystems which require precise timed events
69 separate the "timeout" and "precise timer" subsystems.
|
| /linux/drivers/remoteproc/ |
| H A D | qcom_common.c | 83 struct minidump_subsystem subsystems[MAX_NUM_OF_SS]; member
165 subsystem = &toc->subsystems[minidump_id]; in qcom_minidump()
|
| /linux/Documentation/netlabel/ |
| H A D | introduction.rst | 24 engine will handle those tasks as well. Other kernel subsystems should
|
| /linux/Documentation/driver-api/fpga/ |
| H A D | intro.rst | 5 Linux. Some of the core intentions of the FPGA subsystems are:
|