From: Cedric Le Goater <clg@fr.ibm.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Andrew Morton <akpm@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Serge Hallyn <serue@us.ibm.com>,
Linux Containers <containers@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] A config option to compile out some namespaces code (v3)
Date: Wed, 31 Oct 2007 13:53:44 +0100 [thread overview]
Message-ID: <47287AD8.9050607@fr.ibm.com> (raw)
In-Reply-To: <47285FEE.9030001@openvz.org>
Pavel Emelyanov wrote:
> There were some questions like "do I need this on my cellphone"
> in reply to different namespaces patches. Indeed, the namespaces
> are not useful for most of the embedded systems, but the code
> creating and releasing them weights a lot.
>
> So I propose to add a config option which will help embedded
> people to reduce the vmlinux size. This option simply compiles
> out the namespaces cloning and releasing code *only*, but keeps
> all the other logic untouched (e.g. the notion of init_ns).
>
> When someone tries to clone some namespace with their support
> turned off, he will receive an EINVAL error.
>
> This patchset can save more than 2KB from the vmlinux when
> turning the config option "NAMESPACES" to "n".
>
> I do not introduce the NAMESPACES_EXPERIMENTAL config option, that
> switches all the namespaces we consider experimental, but each
> namespace has its own config that can be mrked with "depends on
> EXPERIMENTAL" on demand.
>
> This is mainly done because some people consider pid namespaces broken
> ant will probably want to make them depend on BROKEN. In this case
> we'll have to introduce the NAMESPACES_BROKEN option which is not that
> good.
I think the discussion finished with an 'immature' status :)
> Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
I'm fine with all these patches and I have a bunch of patches that
depend on them already. The sooner they get in the better.
Thanks Pavel !
C.
prev parent reply other threads:[~2007-10-31 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 10:58 [PATCH 0/5] A config option to compile out some namespaces code (v3) Pavel Emelyanov
2007-10-31 10:58 ` Pavel Emelyanov
[not found] ` <47285FEE.9030001-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-10-31 11:05 ` [PATCH 1/5] The config option itself Pavel Emelyanov
2007-10-31 11:05 ` Pavel Emelyanov
[not found] ` <4728615D.5070700-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-10-31 16:19 ` Randy Dunlap
2007-10-31 16:19 ` Randy Dunlap
[not found] ` <20071031091906.dd84761a.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2007-10-31 17:34 ` Pavel Emelyanov
2007-10-31 17:34 ` Pavel Emelyanov
2007-10-31 22:29 ` Andrew Morton
2007-10-31 11:06 ` [PATCH 2/5] Move the UTS namespace under the option Pavel Emelyanov
2007-10-31 11:06 ` Pavel Emelyanov
2007-10-31 12:58 ` Cedric Le Goater
2007-10-31 14:04 ` Pavel Emelyanov
2007-10-31 11:09 ` [PATCH 4/5] Move the user " Pavel Emelyanov
2007-10-31 11:09 ` Pavel Emelyanov
2007-10-31 11:11 ` [PATCH 5/5] Move the PID " Pavel Emelyanov
2007-10-31 11:11 ` Pavel Emelyanov
2007-10-31 11:08 ` [PATCH 3/5] Move the IPC " Pavel Emelyanov
2007-10-31 12:53 ` Cedric Le Goater [this message]
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=47287AD8.9050607@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=akpm@osdl.org \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.