public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
	Serge Hallyn <serue@us.ibm.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Linux Containers <containers@lists.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/6] A config option to compile out some namespaces code (v4)
Date: Wed, 14 Nov 2007 14:26:19 +0300	[thread overview]
Message-ID: <473ADB5B.50902@openvz.org> (raw)

Change against v3: rebased on 2.6.24-rc2-mm1

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).

Moreover, some of the namespaces might be not 100% ready by
the time of Linux-2.6.xxx release (like user namespaces or pid 
namespaces are now). Since each namespace has its own option, 
which depends on the NAMESPACES, it can be mrked with "depends
on EXPERIMENTAL/BROKEN/ANYTHING_ELSE" not to release the
functionality that is not 100% ready yet.

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".

Signed-off-by: Pavel Emelyanov <xemul@openvz.org>

             reply	other threads:[~2007-11-14 11:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 11:26 Pavel Emelyanov [this message]
2007-11-14 11:28 ` [PATCH 1/6] Add the NAMESPACES config option Pavel Emelyanov
2007-11-14 11:30 ` [PATCH 2/6] Move the UTS namespace under UTS_NS option Pavel Emelyanov
2007-11-14 11:32 ` [PATCH 3/6] Move the IPC namespace under IPC_NS option Pavel Emelyanov
2007-11-14 11:36 ` [PATCH 4/6] Cleanup the code managed with the USER_NS option Pavel Emelyanov
2007-11-14 11:39 ` [PATCH 5/6] Cleanup the code managed with PID_NS option Pavel Emelyanov
2007-11-14 11:41 ` [PATCH 6/6] Mark NET_NS with "depends on NAMESPACES" Pavel Emelyanov
2007-11-14 14:58 ` [PATCH 0/6] A config option to compile out some namespaces code (v4) Serge E. Hallyn

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=473ADB5B.50902@openvz.org \
    --to=xemul@openvz.org \
    --cc=akpm@osdl.org \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    /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