From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Daniel Hokka Zakrisson <daniel@hozac.com>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Andi Kleen <andi@firstfloor.org>,
"David C. Hansen" <haveblue@us.ibm.com>,
linux-kernel@vger.kernel.org, Cedric Le Goater <clg@fr.ibm.com>,
Containers <containers@lists.osdl.org>,
Pavel Emelyanov <xemul@openvz.org>
Subject: Re: [PATCH 1/3] change clone_flags type to u64
Date: Thu, 10 Apr 2008 17:49:47 -0500 [thread overview]
Message-ID: <20080410224947.GA8346@sergelap.austin.ibm.com> (raw)
In-Reply-To: <49365.192.168.101.12.1207865580.squirrel@intranet>
Quoting Daniel Hokka Zakrisson (daniel@hozac.com):
> Serge E. Hallyn wrote:
> > Quoting Andi Kleen (andi@firstfloor.org):
> >> > I guess that was a development rationale.
> >>
> >> But what rationale? It just doesn't make much sense to me.
> >>
> >> > Most of the namespaces are in
> >> > use in the container projects like openvz, vserver and probably others
> >> > and we needed a way to activate the code.
> >>
> >> You could just have added it to feature groups over time.
> >>
> >> >
> >> > Not perfect I agree.
> >> >
> >> > > With your current strategy are you sure that even 64bit will
> >> > > be enough in the end? For me it rather looks like you'll
> >> > > go through those quickly too as more and more of the kernel
> >> > > is namespaced.
> >> >
> >> > well, we're reaching the end. I hope ! devpts is in progress and
> >> > mq is just waiting for a clone flag.
> >>
> >> Are you sure?
> >
> > Well for one thing we can take a somewhat different approach to new
> > clone flags. I.e. we could extend CLONE_NEWIPC to do mq instead of
> > introducing a new clone flag. The name doesn't have 'sysv' in it,
> > and globbing all ipc resources together makes some amount of sense.
> > Similarly has hpa+eric pointed out earlier, suka could use
> > CLONE_NEWDEV for ptys. If we have net, pid, ipc, devices, that's a
> > pretty reasonable split imo. Perhaps we tie user to devices and get
> > rid of CLONE_NEWUSER which I suspect noone is using atm (since only
> > Dave has run into the CONFIG_USER_SCHED problem). Or not. We could
> > roll uts into net, and give CLONE_NEWUTS a deprecation period.
>
> Please don't. Then we'd need to re-add it in Linux-VServer to support
> guests where network namespaces aren't used...
So these are networked vservers with a different hostname? Just
curious, what would be a typical use for these?
Anyway then I guess we won't :) Do you have other suggestions for
ns clone flags which ought to be combined? Do the rest of what I
listed make sense to you? (If not, then I guess I'll step out of the
way and let you and Andi fight it out :)
thanks,
-serge
next prev parent reply other threads:[~2008-04-10 22:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 22:26 [PATCH 0/3] clone64() and unshare64() system calls sukadev
2008-04-09 22:32 ` [PATCH 1/3] change clone_flags type to u64 sukadev
2008-04-10 8:25 ` Andi Kleen
2008-04-10 12:25 ` Cedric Le Goater
2008-04-10 12:52 ` Andi Kleen
2008-04-10 13:11 ` Kirill Korotaev
2008-04-10 13:23 ` Cedric Le Goater
2008-04-10 13:18 ` Cedric Le Goater
2008-04-10 17:14 ` Serge E. Hallyn
2008-04-10 22:13 ` Daniel Hokka Zakrisson
2008-04-10 22:49 ` Serge E. Hallyn [this message]
2008-04-11 8:45 ` Daniel Hokka Zakrisson
2008-04-09 22:34 ` [PATCH 2/3] add do_unshare() sukadev
2008-04-09 22:34 ` [PATCH 3/3] add the clone64() and unshare64() syscalls sukadev
2008-04-09 23:07 ` Jakub Jelinek
2008-04-10 2:15 ` sukadev
2008-04-10 3:40 ` H. Peter Anvin
2008-04-10 0:00 ` [PATCH 0/3] clone64() and unshare64() system calls H. Peter Anvin
2008-04-10 1:07 ` sukadev
2008-04-10 1:10 ` H. Peter Anvin
2008-04-10 2:38 ` sukadev
2008-04-10 2:43 ` Paul Menage
2008-04-10 18:26 ` sukadev
2008-04-10 18:31 ` H. Peter Anvin
2008-04-10 12:33 ` Cedric Le Goater
2008-04-10 16:00 ` H. Peter Anvin
2008-04-10 6:48 ` Cedric Le Goater
-- strict thread matches above, loose matches on Subject: below --
2008-02-11 9:58 [patch 0/3] clone64() and unshare64() syscalls clg
2008-02-11 9:58 ` [patch 1/3] change clone_flags type to u64 clg
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=20080410224947.GA8346@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=andi@firstfloor.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=daniel@hozac.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xemul@openvz.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®