Quoting Eric W. Biederman ([email protected]):
> "Serge E. Hallyn" <[email protected]> writes:
> With respect to pids lets not get caught up in the implementation
> details. Let's first get clear on what the semantics should be.
>
> - Should the first pid in a pid space have pid 1?
>
> - Should pid == 1 ignore signals, it doesn't have a handler for?
>
> - Should any children of pid 1 be allowed to live when pid == 1 is killed?
But doesn't that depend on whether we use (pspace,pid) or vpids? If
vpids, then init isn't really a problem, since from kernelspace
processes in a comtainer stil have a global pid and global parent, and
init knows them. If (pspace,pid), then we need a fakeinit bc the real
init doesn't know about the processes in the container...
> - Should a process have some sort of global (on the machine identifier)?
I think to satisfy openvz existing customers this must be a yes. With
vpid the answer is simple. With (pspace,pid), there are three anwers i've
heard, namely
1. just use pspaceid, pid
2. make pspaceid small and use (pspaceid << SOMEBITS | pid)
3. use pid1/pid2/pid3 where pid1 is creator of pid and its
pspace, etc...
But the openvz guys also don't want userspace tool changes, making (2)
the most likely option. Any other ideas?
> - Should the pids in a pid space be visible from the outside?
Again, the openvz guys say yes.
I think it should be acceptable if a pidspace is visible in all it's
ancestor pidspaces. I.e. if I create pspace2 and pspace3 from pid 234
in pspace1, then pspace2 doesn't need to be able to address pspace3
and vice versa.
Kirill, is that acceptable?
> - Should the parent of pid 1 be able to wait for it for it's
> children?
Yes.
> - Is a completely disjoin pid space acceptable to anyone?
To anyone? yes :)
TO everyone, I don't think so.
> - What should the parent of pid == 1 see?
>
> - Should a process not in the default pid space be able to create
> another pid space?
Yes.
This is to support using pidspaces for vservers, and creating
migrateable sub-pidspaces in each vserver.
> - Should we be able to monitor a pid space from the outside?
To some extent, yes.
> - Should we be able to have processes enter a pid space?
IMO that is crucial.
> - Do we need to be able to be able to ptrace/kill individual processes
> in a pid space, from the outside, and why?
I think this is completely unnecessary so long as a process can enter a
pidspace.
> - After migration what identifiers should the tasks have?
It must be possible to retain the same pids, at least from inside the
container.
So this is irrelevant, as the openvz approach can just virtualize the
old pid, while (pspace, pid) will be able to create a new container and
use the old pid values, which are then guaranteed to not be in use.
> If we can answer these kinds of questions we can likely focus in
> on what the implementation should look like. So far I have not
> seen a question that could not be implemented with a (pspace, pid)/pid
> or a vpid/pid implementation.
But you have, haven't you? Namely, how can openvz provide it's
customers with a global view of all processes without putting 5 years of
work into a new sysadmin interface?
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
