/linux/Documentation/admin-guide/sysctl/ |
H A D | user.rst | 15 limits on the number of namespaces and other objects that have 29 who created user namespaces the creation of the object happens 30 in (user namespaces can be nested) and verified to be below the per user 31 limits in the user namespaces of those users. 41 The maximum number of cgroup namespaces that any user in the current 47 The maximum number of ipc namespaces that any user in the current 53 The maximum number of mount namespaces that any user in the current 59 The maximum number of network namespaces that any user in the 65 The maximum number of pid namespaces that any user in the current 71 The maximum number of time namespaces that any user in the current [all …]
|
/linux/tools/perf/util/ |
H A D | namespaces.c | 7 #include "namespaces.h" 40 struct namespaces *namespaces__new(struct perf_record_namespaces *event) in namespaces__new() 42 struct namespaces *namespaces; in namespaces__new() local 46 namespaces = zalloc(sizeof(struct namespaces) + link_info_size); in namespaces__new() 47 if (!namespaces) in namespaces__new() 50 namespaces->end_time = -1; in namespaces__new() 53 memcpy(namespaces->link_info, event->link_info, link_info_size); in namespaces__new() 55 return namespaces; in namespaces__new() 58 namespaces__free(struct namespaces * namespaces) namespaces__free() argument [all...] |
H A D | namespaces.h | 24 struct namespaces { struct 30 struct namespaces *namespaces__new(struct perf_record_namespaces *event); argument 31 void namespaces__free(struct namespaces *namespaces);
|
H A D | thread.c | 90 struct namespaces *namespaces, *tmp_namespaces; in thread__delete() local 100 list_for_each_entry_safe(namespaces, tmp_namespaces, in thread__delete() 102 list_del_init(&namespaces->list); in thread__delete() 103 namespaces__free(namespaces); in thread__delete() 145 static struct namespaces *__thread__namespaces(struct thread *thread) in __thread__namespaces() 150 return list_first_entry(thread__namespaces_list(thread), struct namespaces, list); in __thread__namespaces() 153 struct namespaces *thread__namespaces(struct thread *thread) in thread__namespaces() 155 struct namespaces *ns; in thread__namespaces() 167 struct namespaces *new, *curr = __thread__namespaces(thread); in __thread__set_namespaces()
|
H A D | synthetic-events.c | 14 #include "util/namespaces.h" 233 memset(&event->namespaces, 0, (sizeof(event->namespaces) + in perf_event__synthesize_namespaces() 237 event->namespaces.pid = tgid; in perf_event__synthesize_namespaces() 238 event->namespaces.tid = pid; in perf_event__synthesize_namespaces() 240 event->namespaces.nr_namespaces = NR_NAMESPACES; in perf_event__synthesize_namespaces() 242 ns_link_info = event->namespaces.link_info; in perf_event__synthesize_namespaces() 244 for (idx = 0; idx < event->namespaces.nr_namespaces; idx++) in perf_event__synthesize_namespaces() 248 event->namespaces.header.type = PERF_RECORD_NAMESPACES; in perf_event__synthesize_namespaces() 250 event->namespaces in perf_event__synthesize_namespaces() [all...] |
H A D | thread.h | 70 struct namespaces; 90 struct namespaces *thread__namespaces(struct thread *thread);
|
/linux/Documentation/admin-guide/namespaces/ |
H A D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces. 10 in different other namespaces (the rows): 23 1. Both the IPC and the PID namespaces provide IDs to address 33 2. Intentionally, two equal user IDs in different user namespaces 39 The same is true for the IPC namespaces being shared - two users 40 from different user namespaces should not access the same IPC objects
|
H A D | resource-control.rst | 7 of processes is allowed to switch user ids. With user namespaces 12 kernels that enable user namespaces, and it is further recommended
|
/linux/tools/testing/selftests/net/forwarding/ |
H A D | README | 4 One of the nice things about network namespaces is that they allow one 7 Unfortunately, these namespaces can not be used with actual switching 8 ASICs, as their ports can not be migrated to other network namespaces 10 L1-separation provided by namespaces. 26 The VRFs act as lightweight namespaces representing hosts connected to
|
/linux/Documentation/core-api/ |
H A D | symbol-namespaces.rst | 24 their exported symbols into separate namespaces. That is useful for 27 kernel. As of today, modules that make use of symbols exported into namespaces, 60 Defining namespaces for all symbols of a subsystem can be very verbose and may 89 In order to use symbols that are exported into namespaces, kernel modules need 90 to explicitly import these namespaces. Otherwise the kernel might reject to 92 for the namespaces it uses symbols from. E.g. a module using the 99 This has the side effect, that the imported namespaces of a module can be 127 Missing namespaces imports can easily be detected at build time. In fact,
|
/linux/tools/testing/selftests/net/ |
H A D | pmtu.sh | 1162 setup namespaces routing || return $ksft_skip 1256 setup namespaces policy_routing || return $ksft_skip 1301 setup namespaces policy_routing || return $ksft_skip 1349 setup namespaces routing ${type}4 || return $ksft_skip 1353 setup namespaces routing ${type}6 || return $ksft_skip 1424 setup namespaces routing bridge bridged_${type}4 || return $ksft_skip 1428 setup namespaces routing bridge bridged_${type}6 || return $ksft_skip 1549 setup namespaces routing ovs_bridge ovs_${type}4 || return $ksft_skip 1553 setup namespaces routing ovs_bridge ovs_${type}6 || return $ksft_skip 1630 setup namespaces routing ${encap}${outer_family}${inner_family} || return $ksft_skip [all …]
|
/linux/Documentation/translations/zh_CN/core-api/ |
H A D | symbol-namespaces.rst | 3 :Original: Documentation/core-api/symbol-namespaces.rst 9 .. _cn_symbol-namespaces.rst:
|
H A D | index.rst | 32 symbol-namespaces
|
/linux/tools/testing/selftests/drivers/net/bonding/ |
H A D | lag_lib.sh | 91 local namespaces="lag_node1 lag_node2" 94 for n in ${namespaces}; do 107 NAMESPACES="${namespaces}"
|
/linux/Documentation/admin-guide/LSM/ |
H A D | SafeSetID.rst | 66 Use user namespaces 73 Unfortunately, it is not generally feasible to use user namespaces in isolation, 76 entity. For example, Linux has the notion that network namespaces are owned by 85 configurations. Using user namespaces in isolation causes problems regarding 86 other system interactions, including use of pid namespaces and device creation.
|
/linux/Documentation/networking/ |
H A D | sysfs-tagging.rst | 15 namespaces to see the same interface that is currently presented in 35 the contents of other namespaces' sysfs mounts. Therefore, when a
|
H A D | netfilter-sysctl.rst | 17 namespaces. This variable is only accessible from init_net.
|
H A D | ipvlan.rst | 15 driver in conjunction with network namespaces and not sure if there is use case 156 (a) Create two network namespaces - ns0, ns1:: 166 (c) Assign slaves to the respective network namespaces::
|
/linux/Documentation/translations/it_IT/core-api/ |
H A D | index.rst | 11 symbol-namespaces
|
/linux/scripts/ |
H A D | nsdeps | 33 for ns in $namespaces; do
|
/linux/drivers/nvme/target/ |
H A D | core.c | 130 nvmet_for_each_enabled_ns(&subsys->namespaces, idx, cur) in nvmet_max_nsid() 443 req->ns = xa_load(&subsys->namespaces, nsid); in nvmet_req_find_ns() 614 xa_set_mark(&subsys->namespaces, ns->nsid, NVMET_NS_ENABLED); in nvmet_ns_enable() 640 xa_clear_mark(&subsys->namespaces, ns->nsid, NVMET_NS_ENABLED); in nvmet_ns_disable() 678 xa_erase(&subsys->namespaces, ns->nsid); in nvmet_ns_free() 714 if (xa_insert(&subsys->namespaces, ns->nsid, ns, GFP_KERNEL)) in nvmet_ns_alloc() 1514 nvmet_for_each_enabled_ns(&ctrl->subsys->namespaces, idx, ns) in nvmet_setup_p2p_ns_map() 1834 xa_init(&subsys->namespaces); in nvmet_subsys_alloc() 1860 WARN_ON_ONCE(!xa_empty(&subsys->namespaces)); in nvmet_subsys_free() 1864 xa_destroy(&subsys->namespaces); in nvmet_subsys_free()
|
/linux/include/net/ |
H A D | ioam6.h | 44 struct rhashtable namespaces; member
|
/linux/Documentation/driver-api/nvdimm/ |
H A D | nvdimm.rst | 83 (persistently names) capacity allocated to different PMEM namespaces. It 523 Idle namespaces are automatically created by the kernel if a given 544 /* unlike pmem namespaces, blk namespaces have a sector size */ 559 https://www.nvmexpress.org/specifications/), and NFIT namespaces are 561 NVME-namespaces. 593 Similar to namespaces an idle BTT device is automatically created per
|
/linux/fs/proc/ |
H A D | Makefile | 27 proc-y += namespaces.o
|
/linux/lib/vdso/ |
H A D | Kconfig | 30 Selected by architectures which support time namespaces in the
|