From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Kirill Korotaev <dev@sw.ru>,
"Dave Hansen <haveblue@us.ibm.com> Cedric Le Goater"
<clg@fr.ibm.com>, Herbert Poetzl <herbert@13thfloor.at>,
linux-kernel@vger.kernel.org
Subject: Re: question: pid space semantics.
Date: Tue, 14 Mar 2006 13:21:25 -0700 [thread overview]
Message-ID: <m1ek14lquy.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1142363896.28604.43.camel@localhost.localdomain> (Dave Hansen's message of "Tue, 14 Mar 2006 11:18:16 -0800")
Dave Hansen <haveblue@us.ibm.com> writes:
> On Tue, 2006-03-14 at 11:43 -0700, Eric W. Biederman wrote:
>> 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?
>
> So, you'd basically only allocate the cross-namespace pids when you
> needed to do some kind of cross-namespace management?
Yes, or setup a parent/child relationship. So I think the first
process in a container would always get two pids.
> pid_t alloc_local_pid(container_handle, pid_t pid_inside_container)
That is the idea.
I actually expect the implementation to look very much different.
To me the nice piece of this concept is that it allows all pids
to local to a pid space while still be able to talk to remote
processes.
Eric
next prev parent reply other threads:[~2006-03-14 20:22 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
2006-03-14 19:18 ` Dave Hansen
2006-03-14 20:21 ` Eric W. Biederman [this message]
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=m1ek14lquy.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=haveblue@us.ibm.com \
--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
all inboxes | Powered by JetHome®