Lines Matching +full:power +full:- +full:stable +full:- +full:time

10 ----------
14 --------
26 -----------
35 power of implementing threads in this manner comes not only from
37 outside the confinement of all-or-nothing shared resources of legacy
38 threads. On Linux, at the time of thread creation using the clone system
44 shared at the time of their creation. unshare() was conceptualized by
45 Al Viro in the August of 2000, on the Linux-Kernel mailing list, as part
53 -----------
59 even non-threaded applications if they have a need to disassociate
60 from default shared namespace. The following lists two use-cases
63 2.1 Per-security context namespaces
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
68 such as per-user and/or per-security context instance of /tmp, /var/tmp or
69 per-security context instance of a user's home directory, isolate user
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
93 -------
100 stable code to implement a new feature that may not get exercised
106 ---------------
123 ---------------------------
126 	unshare - disassociate parts of the process execution context
145 	The flags argument specifies one or bitwise-or'ed of several of
166 	On success, zero returned. On failure, -1 is returned and errno is
169 	EPERM	CLONE_NEWNS was specified by a non-root process (process
178 	The unshare() call is Linux-specific and  should  not be used
185 --------------------
194   1) clone operates on a newly allocated not-yet-active task
232 -------------------
284 and CLONE_THREAD, return -EINVAL since they are not implemented yet.
297 ---------------------
303      yet, return -EINVAL.
323 --------------