Searched refs:containers (Results 1 – 16 of 16) sorted by relevance
| /linux-5.19.10/drivers/base/ |
| D | attribute_container.c | 76 klist_init(&cont->containers, internal_container_klist_get, in attribute_container_register()
98 spin_lock(&cont->containers.k_lock); in attribute_container_unregister()
99 if (!list_empty(&cont->containers.k_list)) in attribute_container_unregister()
104 spin_unlock(&cont->containers.k_lock); in attribute_container_unregister()
174 klist_add_tail(&ic->node, &cont->containers); in attribute_container_add_device()
224 klist_for_each_entry(ic, &cont->containers, node, &iter) { in attribute_container_remove_device()
254 klist_for_each_entry(ic, &cont->containers, node, &iter) { in do_attribute_container_device_trigger_safe()
271 klist_for_each_entry(ic, &cont->containers, node, &iter) { in do_attribute_container_device_trigger_safe()
373 klist_for_each_entry(ic, &cont->containers, node, &iter) { in attribute_container_device_trigger()
537 klist_for_each_entry(ic, &cont->containers, node, &iter) { in attribute_container_find_class_device()
|
| /linux-5.19.10/Documentation/networking/ |
| D | netfilter-sysctl.rst | 15 with LOG target; this aims to prevent containers from flooding host
|
| /linux-5.19.10/drivers/gpu/drm/omapdrm/ |
| D | omap_dmm_tiler.c | 34 static struct tcm *containers[TILFMT_NFORMATS]; variable
554 ret = tcm_reserve_2d(containers[fmt], w, h, align, -1, slot_bytes, in tiler_reserve_2d()
580 if (tcm_reserve_1d(containers[TILFMT_PAGE], num_pages, in tiler_reserve_1d()
935 containers[TILFMT_8BIT] = omap_dmm->tcm[0]; in omap_dmm_probe()
936 containers[TILFMT_16BIT] = omap_dmm->tcm[0]; in omap_dmm_probe()
937 containers[TILFMT_32BIT] = omap_dmm->tcm[0]; in omap_dmm_probe()
943 containers[TILFMT_PAGE] = omap_dmm->tcm[1]; in omap_dmm_probe()
947 containers[TILFMT_PAGE] = omap_dmm->tcm[0]; in omap_dmm_probe()
|
| /linux-5.19.10/include/linux/ |
| D | attribute_container.h | 18 struct klist containers; member
|
| /linux-5.19.10/Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 9 proxy device driver for Linux containers.
|
| /linux-5.19.10/fs/erofs/ |
| D | Kconfig | 14 numerous containers;
|
| /linux-5.19.10/Documentation/filesystems/ext4/ |
| D | allocators.rst | 44 groups; these mini-containers are used as outlined above to try to
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | erofs.rst | 31 hosts with numerous containers.
70 - Support FSDAX on uncompressed images for secure containers and ramdisks in
|
| D | idmappings.rst | 545 workloads. For a more complex but common example, consider two containers
546 started on the host. To completely prevent the two containers from affecting
548 for the two containers::
561 to both containers currently can't.
599 between two containers with different idmappings.
601 aren't mountable inside containers. And not having them mountable might be
|
| /linux-5.19.10/Documentation/admin-guide/nfs/ |
| D | nfs-client.rst | 58 containers unless it is overridden by a value written to
|
| /linux-5.19.10/Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 72 devices supported by ACPI, such as containers, memory modules,
|
| /linux-5.19.10/Documentation/filesystems/nfs/ |
| D | client-identifier.rst | 158 distinction between network namespaces (containers) when the
|
| /linux-5.19.10/Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 139 nodes are leaf nodes, otherwise they become containers of
|
| /linux-5.19.10/Documentation/userspace-api/ |
| D | landlock.rst | 429 What about namespaces and containers?
|
| /linux-5.19.10/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 680 in containers and systemd for assorted meta data like main PID in a cgroup
|
| /linux-5.19.10/init/ |
| D | Kconfig | 1228 This allows containers, i.e. vservers, to use user namespaces
1244 pid namespaces. This is a building block of containers.
|