From: ebiederm@xmission.com (Eric W. Biederman)
To: Kirill Korotaev <dev@sw.ru>
Cc: "Dave Hansen <haveblue@us.ibm.com> Cedric Le Goater"
<clg@fr.ibm.com>, Herbert Poetzl <herbert@13thfloor.at>,
<linux-kernel@vger.kernel.org>
Subject: question: pid space semantics.
Date: Tue, 14 Mar 2006 11:43:38 -0700 [thread overview]
Message-ID: <m1veuglvdx.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1142282940.27590.17.camel@localhost.localdomain> (Dave Hansen's message of "Mon, 13 Mar 2006 12:48:59 -0800")
To retain any part of the existing unix process management
we need some processes that show up in multiple pid spaces.
To allow for migration it must be possible for the pids in those pid
spaces to be different.
It is undesirable in the normal case of affairs to allocate more
than one pid per process.
Given the small range of pid values these constraints make an
efficient and general pid space solution challenging.
The question:
If we could add additional pid values in different pid spaces to a
process with a syscall upon demand would that lead to an
implementation everyone could use?
I assume most processes by default only have a pid value in a single
pid space.
The reason I ask is that I believe I know how to implement a cheap
general mechanism for adding additional pids to a process.
Eric
next parent reply other threads:[~2006-03-14 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1142282940.27590.17.camel@localhost.localdomain>
2006-03-14 18:43 ` Eric W. Biederman [this message]
2006-03-14 19:18 ` Dave Hansen
2006-03-14 20:21 ` Eric W. Biederman
2006-03-14 20:32 ` Cedric Le Goater
2006-03-14 22:40 ` Herbert Poetzl
2006-03-15 6:01 ` Eric W. Biederman
2006-03-15 4:27 ` Ulrich Drepper
2006-03-15 5:37 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1veuglvdx.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome