Lines Matching refs:shared

36 outside the confinement of all-or-nothing shared resources of legacy
43 shared at the time of their creation. unshare was conceptualized by
47 shared resources without creating a new process. unshare is a natural
55 resources is not possible. Since namespaces are shared by default
58 from default shared namespace. The following lists two use-cases
71 of shared-tree feature in the Linux kernel, even regular Linux systems
81 decide what needs to be shared at the time of creating the process
105 be shared, similar flags in unshare(int flags) should specify
128 	context that are currently being shared with other processes. Part
129 	of execution context, such as the namespace, is shared by default
132 	shared by explicit request to share them when creating a process
136 	shared execution context without creating a new process.
143 		is disassociated from the shared file system information.
147 		caller is disassociated from the shared file descriptor
152 		disassociated from the shared namespace.
156 		disassociated from the shared virtual memory.
181 the current shared version, associates newly duplicated structures
182 with the current task structure and releases corresponding shared
191      current task and releasing older shared structures. Failure
198      system call will have to go back to older, shared, vm
215   4) Appropriately release older, shared, context structures.
242 	 set and signals are also being shared, force CLONE_THREAD. If
252          older, shared, structures.
279   4) Concurrent execution: Use shared memory segments and futex on