Re: [RFC] [PATCH 00/13] Introduce task_pid api

[Serge E. Hallyn]

Quoting Paul Jackson (pj@xxxxxxx):
> Serge wrote:
> > the vserver model
> 
> What's that?

:)  Well a vserver pretends to be a full system of its own, though you
can have lots of vservers on one machine.  Processes in each virtual
server see only other processes in the same vserver.  However in
vserver the pids they see are the real kernel pids - except for one
process per vserver which can be the fakeinit.  Other processes in the
same vserver see it as pid 1, but to the kernel it is still known by
its real pid.

> How large is our numeric pid space (on 64 bit systems, anyway)?  If
> large enough, then reservation of pid ranges becomes an easy task.  If
> say we had 10 bits to spare, then a server farm could pre-ordain say a
> thousand virtual servers, which come and go on various hardware
> systems, each virtual server with its own hostname, pid-range, and
> other such paraphernalia.

In fact this is one way we considered implementing the virtual pids -
the pidspace id would be the upper some bits of the pid, and the vpid
would be the lower bits, so that the kernel pid would simply be
(pidspace_id << some_shift | vpid).

-serge

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/