Lines Matching full:shared

37 outside the confinement of all-or-nothing shared resources of legacy
44 shared at the time of their creation. unshare() was conceptualized by
48 shared resources without creating a new process. unshare() is a natural
57 resources is not possible. Since namespaces are shared by default
60 from default shared namespace. The following lists two use-cases
74 of shared-tree feature in the Linux kernel, even regular Linux systems
85 decide what needs to be shared at the time of creating the process
111 be shared, similar flags in unshare(int flags) should specify
135 	context that are currently being shared with other processes. Part
136 	of execution context, such as the namespace, is shared by default
139 	shared by explicit request to share them when creating a process
143 	shared execution context without creating a new process.
150 		is disassociated from the shared file system information.
154 		caller is disassociated from the shared file descriptor
159 		disassociated from the shared namespace.
163 		disassociated from the shared virtual memory.
189 the current shared version, associates newly duplicated structures
190 with the current task structure and releases corresponding shared
201      current task and releasing older shared structures. Failure
208      system call will have to go back to older, shared, vm
229   4) Appropriately release older, shared, context structures.
265 	 set and signals are also being shared, force CLONE_THREAD. If
278          older, shared, structures.
315   4) Concurrent execution: Use shared memory segments and futex on