From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Re: [RFC] PATCH 0/4 - Time virtualization
Date: Fri, 28 Apr 2006 07:48:23 -0400 [thread overview]
Message-ID: <20060428114823.GA3641@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200604281333.41358.blaisorblade@yahoo.it>
On Fri, Apr 28, 2006 at 01:33:40PM +0200, Blaisorblade wrote:
> > So, maybe it belongs in clone as a "backwards" flag similar to
> > CLONE_NEWNS.
>
> I must note that currently every (?) flag allowed for unshare is also allowed
> for clone, so you need to do that anyway.
Currently. We are running out of CLONE_ bits - in mainline, there are
three left, and two of them are likely to be used by CLONE_TIME and
CLONE_UTSNAME (or whatever that turns out to be called).
I'm eyeing the low eight bits (CSIGNAL) for future unshare flags, but
those would be unusable in clone().
And why should there be any overlap between clone flags and unshare
flags? Isn't
clone(CLONE_TIME);
the same as
clone();
unshare(CLONE_TIME);
?
Jeff
next prev parent reply other threads:[~2006-04-28 12:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 17:19 [RFC] PATCH 0/4 - Time virtualization Jeff Dike
2006-04-14 0:31 ` john stultz
2006-04-14 1:53 ` [uml-devel] " Jeff Dike
2006-04-14 16:24 ` john stultz
2006-04-19 8:25 ` Eric W. Biederman
2006-04-26 18:01 ` Jeff Dike
2006-04-28 11:33 ` [uml-devel] " Blaisorblade
2006-04-28 11:48 ` Jeff Dike [this message]
2006-04-28 12:14 ` Jeff Dike
2006-04-28 13:54 ` Blaisorblade
2006-04-28 15:15 ` Jeff Dike
2006-04-28 20:10 ` Blaisorblade
2006-04-28 16:18 ` 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=20060428114823.GA3641@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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