Searched refs:namespace (Results 1 – 25 of 108) sorted by relevance
12345
| /Linux-v4.19/Documentation/sysctl/ |
| D | user.txt | 11 per user per user namespace limits.
19 The creation of per user per user namespace objects are charged to
20 the user in the user namespace who created the object and
21 verified to be below the per user limit in that user namespace.
29 user namespace does not allow a user to escape their current limits.
36 user namespace may create.
41 user namespace may create.
46 user namespace may create.
51 current user namespace may create.
56 user namespace may create.
[all …]
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 8 namespace active multiple devices with the same name can show up in
15 By using the network namespace pointers as tags to separate out the
20 Each sysfs directory entry may be tagged with a namespace via the
23 and KOBJ_NS_TYPES, and ns will point to the namespace to which it
27 *ns[KOBJ_NS_TYPES]. When a task in a tagging namespace
30 s_fs_info->ns[kobj_nstype] set to the new namespace. Note that
33 namespace exits, it will call kobj_ns_exit() to invalidate any
39 - current_ns() which returns current's namespace
40 - netlink_ns() which returns a socket's namespace
|
| D | sharedsubtree.txt | 20 A process wants to clone its own namespace, but still wants to access the CD
24 It provides the necessary building blocks for features like per-user-namespace
152 A) A process wants to clone its own namespace, but still wants to
161 Now any process that clones off a new namespace will have a
163 parent namespace.
179 A new process can clone off a new namespace. And mark some part
180 of its namespace as slave
185 process will not show up in any other namespace. However mounts
186 done in the parent namespace under /myprivatetree still shows
187 up in the process's namespace.
[all …]
|
| D | quota.txt | 35 Since the quota netlink protocol is not namespace aware, quota netlink messages
36 are sent only in initial network namespace.
|
| /Linux-v4.19/Documentation/acpi/ |
| D | namespace.txt | 9 The Linux ACPI subsystem converts ACPI namespace objects into a Linux
39 data structure called the ACPI namespace whose topology reflects the
79 All definition blocks are loaded into a single namespace. The namespace
82 namespace:
88 5. The '\' symbol represents the root of the namespace (i.e. names
89 prepended with '\' are relative to the namespace root).
90 6. The '^' symbol represents the parent of the current namespace node
92 current namespace node).
94 The figure below shows an example ACPI namespace.
101 +-| _PR | Scope(_PR): the processor namespace
[all …]
|
| D | scan_handlers.txt | 6 During system initialization and ACPI-based device hot-add, the ACPI namespace
9 registered with the driver core for every device object in the ACPI namespace
10 and the hierarchy of those struct acpi_device objects reflects the namespace
11 layout (i.e. parent device objects in the namespace are represented by parent
20 The core ACPI namespace scanning code in drivers/acpi/scan.c carries out basic
48 The namespace scanning function, acpi_bus_scan(), first registers all of the
49 device nodes in the given namespace scope with the driver core. Then, it tries
62 the namespace scan should be terminated due to a serious error. The error code
65 The namespace trimming function, acpi_bus_trim(), first executes .detach()
66 callbacks from the scan handlers of all device nodes in the given namespace
[all …]
|
| D | enumeration.txt | 8 SoC/Chipset to appear only in ACPI namespace. These are typically devices
27 the ACPI namespace.
30 enumerated from ACPI namespace. This handle can be used to extract other
146 Here is what the ACPI namespace for a SPI slave might look like:
340 parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
350 If the ACPI namespace has a device that we can match using an ACPI id or ACPI
368 Device Tree namespace link device ID
373 regarded as a device identification namespace analogous to the ACPI/PNP device
374 ID namespace. Consequently, in principle it should not be necessary to allocate
376 identification string in the Device Tree (DT) namespace, especially if that ID
[all …]
|
| D | aml-debugger.txt | 64 the entire ACPI namespace:
66 # acpidbg -b "namespace"
|
| /Linux-v4.19/Documentation/sphinx/ |
| D | load_config.py | 9 def loadConfig(namespace): argument
21 and os.path.normpath(namespace["__file__"]) != os.path.normpath(config_file) ):
26 config = namespace.copy()
30 namespace.update(config)
|
| /Linux-v4.19/Documentation/namespaces/ |
| D | compatibility-list.txt | 7 occur when tasks share some namespace (the columns) while living
23 other task living in a different namespace via a shared filesystem
25 within the namespace it was obtained in and may refer to some
26 other object in another namespace.
30 words, user 10 in one user namespace shouldn't have the same
32 namespace.
|
| /Linux-v4.19/tools/testing/selftests/tc-testing/plugin-lib/ |
| D | nsPlugin.py | 19 if self.args.namespace:
28 if self.args.namespace:
46 if not self.args.namespace:
81 if self.args.namespace:
103 if self.args.namespace:
|
| /Linux-v4.19/tools/perf/util/c++/ |
| D | clang.h | 11 namespace perf {
13 using namespace llvm;
|
| /Linux-v4.19/drivers/nvdimm/ |
| D | Kconfig | 12 namespaces (/dev/ndblkX.Y). A PMEM namespace refers to a
14 (see CONFIG_DAX). A BLK namespace refers to an NVDIMM control
68 NVDIMM namespace, i.e. a namespace can be in raw mode (pmemX,
98 namespace. For environments that want to hard partition
100 sub-divide a namespace into character devices that can only be
|
| /Linux-v4.19/Documentation/nvdimm/ |
| D | nvdimm.txt | 32 libnvdimm: namespace
33 libndctl: namespace enumeration example
34 libndctl: namespace creation example
35 Why the Term "namespace"?
192 BLK-namespace can be configured with a BTT with unique atomic sector
194 not provide for a sector size to be specified for a PMEM namespace.
229 single PMEM namespace is created in the REGION0-SPA-range that spans most
239 well as DIMM2 and DIMM3. Some of REGION1 is allocated to a PMEM namespace
432 "nstype" indicates the integer type of namespace-device this region
520 1. There are already more than two REGION and "namespace" types. For
[all …]
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-firmware_node | 15 namespace. This attribute is read-only. If the device does not have
16 an _STR method associated with it in the ACPI namespace, this
|
| D | sysfs-devices-sun | 6 method in the ACPI namespace. The value is written in Advanced
|
| /Linux-v4.19/Documentation/userspace-api/ |
| D | unshare.rst | 60 from default shared namespace. The following lists two use-cases
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
71 module can easily setup a private namespace for a user at login.
136 of execution context, such as the namespace, is shared by default
158 If CLONE_NEWNS is set, the namespace of the caller is
159 disassociated from the shared namespace.
204 both virtual memory and namespace. After successfully unsharing
206 new namespace structure, the error return code will have to
306 namespace without specifying unsharing of filesystem, correctly
307 unshares both namespace and filesystem information.
[all …]
|
| /Linux-v4.19/tools/testing/selftests/tc-testing/ |
| D | README | 6 execute them inside a network namespace dedicated to the task.
15 * The kernel must have network namespace support
57 namespace to prevent conflicts within the host.
155 options for nsPlugin (run commands in net namespace)
157 -n, --namespace
158 Run commands in namespace as specified in tdc_config.py
226 sets up a network namespace and runs all commands in that namespace
|
| /Linux-v4.19/scripts/gdb/linux/ |
| D | proc.py | 162 namespace = task['nsproxy']['mnt_ns']
163 if not namespace:
166 for vfs in lists.list_for_each_entry(namespace['list'],
|
| /Linux-v4.19/kernel/cgroup/ |
| D | Makefile | 2 obj-y := cgroup.o rstat.o namespace.o cgroup-v1.o
|
| /Linux-v4.19/ipc/ |
| D | Makefile | 10 obj-$(CONFIG_IPC_NS) += namespace.o
|
| /Linux-v4.19/Documentation/networking/ |
| D | netfilter-sysctl.txt | 7 By default, only init_net namespace can log packets into kernel log
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 174 through remount from the init namespace. The mount option is
175 ignored on non-init namespace mounts. Please refer to the
453 cgroup namespace on namespace creation.
460 "cgroup.subtree_control" on a namespace root from inside the
461 namespace.
514 namespace of the process which is attempting the migration. If either
1702 cgroup namespace provides a mechanism to virtualize the view of the
1705 namespace. The process running inside the cgroup namespace will have
1708 the cgroup namespace.
1710 Without cgroup namespace, the "/proc/$PID/cgroup" file shows the
[all …]
|
| /Linux-v4.19/Documentation/PCI/ |
| D | acpi-info.txt | 3 The general rule is that the ACPI namespace should describe everything the
7 host bridges, so the ACPI namespace must describe each host bridge, the
21 namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
30 know early in boot, before it can parse the ACPI namespace. If a new table
77 (1) not claimed by _CRS under any other device object in the ACPI namespace
153 namespace (under \_SB) in a node with a _HID of EISAID (PNP0C02), and
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | perf-buildid-cache.txt | 73 Obtain mount namespace information from the target pid. This is
75 different mount namespace from the perf(1) utility.
|
12345
