| /linux-4.4.14/Documentation/namespaces/ |
| D | compatibility-list.txt | 4 may have when creating tasks living in different namespaces.
8 in different other namespaces (the rows):
18 1. Both the IPC and the PID namespaces provide IDs to address
28 2. Intentionally, two equal user IDs in different user namespaces
34 The same is true for the IPC namespaces being shared - two users
35 from different user namespaces should not access the same IPC objects
|
| D | resource-control.txt | 3 of processes is allowed to switch user ids. With user namespaces
8 kernels that enable user namespaces, and it is further recommended
|
| /linux-4.4.14/net/ |
| D | sysctl_net.c | 30 net_ctl_header_lookup(struct ctl_table_root *root, struct nsproxy *namespaces) in net_ctl_header_lookup() argument
32 return &namespaces->net_ns->sysctls; in net_ctl_header_lookup()
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | sysfs-fs-lustre | 307 What: /sys/fs/lustre/ldlm/namespaces/<name>/resource_count
314 What: /sys/fs/lustre/ldlm/namespaces/<name>/lock_count
320 What: /sys/fs/lustre/ldlm/namespaces/<name>/lru_size
329 What: /sys/fs/lustre/ldlm/namespaces/<name>/lock_unused_count
336 What: /sys/fs/lustre/ldlm/namespaces/<name>/lru_max_age
343 What: /sys/fs/lustre/ldlm/namespaces/<name>/early_lock_cancel
356 What: /sys/fs/lustre/ldlm/namespaces/<name>/pool/granted
362 What: /sys/fs/lustre/ldlm/namespaces/<name>/pool/grant_rate
369 What: /sys/fs/lustre/ldlm/namespaces/<name>/pool/cancel_rate
376 What: /sys/fs/lustre/ldlm/namespaces/<name>/pool/grant_speed
[all …]
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 12 namespaces to see the same interface that is currently presented in
32 the contents of other namespaces' sysfs mounts. Therefore, when a
|
| D | 00-INDEX | 129 - a description of shared subtrees for namespaces.
|
| D | sharedsubtree.txt | 167 namespaces.
196 namespaces. But namespaces are associated with processes. If
197 namespaces are made first class objects with user API to
|
| /linux-4.4.14/Documentation/networking/ |
| D | ipvlan.txt | 11 driver in conjuntion with network namespaces and not sure if there is use case
81 (a) Create two network namespaces - ns0, ns1
89 (c) Assign slaves to the respective network namespaces
|
| D | vrf.txt | 17 In addition, VRF devices allow VRFs to be nested within namespaces. For
18 example network namespaces provide separation of network interfaces at L1
|
| D | netdev-features.txt | 145 network namespaces (e.g. loopback).
|
| D | ip-sysctl.txt | 35 only intended to secure e.g. name servers in namespaces where
119 is reached. This also serves as a maximum limit to namespaces
|
| /linux-4.4.14/fs/proc/ |
| D | Makefile | 24 proc-y += namespaces.o
|
| D | proc_sysctl.c | 75 struct ctl_table **pentry, struct nsproxy *namespaces);
322 lookup_header_set(struct ctl_table_root *root, struct nsproxy *namespaces) in lookup_header_set() argument
326 set = root->lookup(root, namespaces); in lookup_header_set()
978 struct ctl_table **pentry, struct nsproxy *namespaces) in sysctl_follow_link() argument
990 set = lookup_header_set(root, namespaces); in sysctl_follow_link()
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | nvdimm.txt | 191 reasons to allow multiple BLK namespaces per REGION is so that each
233 reclaimed space we create two BLK-aperture "namespaces" from REGION2 and
240 named "pm1.0", the rest is reclaimed in 4 BLK-aperture namespaces (for
246 offset (b) are also included in the "blk4.0" and "blk5.0" namespaces.
247 Note, that this example shows that BLK-aperture namespaces don't need to
527 2. A region with zero child-namespaces is a possible configuration. For
569 the resulting namespaces. The output from module resolution is more
677 Idle namespaces are automatically created by the kernel if a given
698 /* unlike pmem namespaces, blk namespaces have a sector size */
712 http://www.nvmexpress.org/specifications/), and NFIT namespaces are
[all …]
|
| /linux-4.4.14/drivers/nvdimm/ |
| D | Kconfig | 10 namespaces (/dev/pmemX) and BLK (sliding mmio window(s))
11 namespaces (/dev/ndblkX.Y). A PMEM namespace refers to a
|
| /linux-4.4.14/drivers/nvme/host/ |
| D | nvme.h | 52 struct list_head namespaces; member
|
| D | pci.c | 2272 list_add_tail(&ns->list, &dev->namespaces); in nvme_alloc_ns()
2524 list_for_each_entry(ns, &dev->namespaces, list) { in nvme_find_ns()
2577 list_for_each_entry_safe(ns, next, &dev->namespaces, list) { in nvme_scan_namespaces()
2581 list_sort(NULL, &dev->namespaces, ns_cmp); in nvme_scan_namespaces()
2934 list_for_each_entry(ns, &dev->namespaces, list) { in nvme_freeze_queues()
2950 list_for_each_entry(ns, &dev->namespaces, list) { in nvme_unfreeze_queues()
2998 list_for_each_entry_safe(ns, next, &dev->namespaces, list) in nvme_dev_remove()
3111 if (list_empty(&dev->namespaces)) in nvme_dev_ioctl()
3113 ns = list_first_entry(&dev->namespaces, struct nvme_ns, list); in nvme_dev_ioctl()
3316 INIT_LIST_HEAD(&dev->namespaces); in nvme_probe()
|
| /linux-4.4.14/include/linux/ |
| D | sysctl.h | 158 struct nsproxy *namespaces);
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 11 into separate namespaces through the use of a vendor
|
| /linux-4.4.14/Documentation/ |
| D | unshare.txt | 55 resources is not possible. Since namespaces are shared by default
61 2.1 Per-security context namespaces
72 can benefit from setting up private namespaces at login and
|
| D | 00-INDEX | 330 namespaces/
331 - directory with various information about namespaces
|
| /linux-4.4.14/Documentation/security/ |
| D | Yama.txt | 44 so that any otherwise allowed process (even those in external pid namespaces)
|
| D | Smack.txt | 499 namespaces and access requests are only required to match the object in
|
| /linux-4.4.14/Documentation/acpi/ |
| D | enumeration.txt | 382 belong to one of the namespaces prescribed by the ACPI specification (see
387 be a device ID from one of the namespaces prescribed by the specification too.
|
| /linux-4.4.14/fs/ |
| D | Kconfig | 159 security.* namespaces.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 1176 different namespaces.
1193 different IPC objects in different namespaces.
1199 This allows containers, i.e. vservers, to use user namespaces
1202 When user namespaces are enabled in the kernel it is
1214 Support process id namespaces. This allows having multiple
1216 pid namespaces. This is a building block of containers.
|
| /linux-4.4.14/drivers/tty/ |
| D | Kconfig | 129 If you want to have isolated PTY namespaces (eg: in containers),
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 85 namespaces. These all require the basic notion of a
|
| /linux-4.4.14/Documentation/gpio/ |
| D | gpio-legacy.txt | 382 two logically distinct namespaces (GPIO 0 need not use IRQ 0). You can
|