From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: "Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
Serge Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: Playing with namespaces and bloat-o-meeter
Date: Wed, 26 Sep 2007 18:49:42 +0400 [thread overview]
Message-ID: <46FA7186.1070202@openvz.org> (raw)
In-Reply-To: <m1y7etv634.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
Eric W. Biederman wrote:
> Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org> writes:
>
>>>
>>> +config NAMESPACES
>>> + bool "The namespaces support"
>>> + help
>>> + Provides the way to make tasks work with different objects using
>>> + the same id
>>> +
>>> +config NS_UTS
>>> + bool "Uname namespace"
>>> + depends on NAMESPACES
>>> + help
>>> + The utsname namespace
>>> +
>>> +config NS_IPC
>>> + bool "IPC namespace"
>>> + depends on NAMESPACES && SYSVIPC
>>> + help
>>> + The SYSVIPC ids namespaces
>>> +
>>> +config NS_PIDS
>>> + bool "PID namespace"
>>> + depends on NAMESPACES
>>> + help
>>> + Tasks see only the pids living in the same namespace and in the
>>> + child namespaces
>>> +
>>> +config NS_UID
>>> + bool "UID namespace"
>>> + depends on NAMESPACES && EXPERIMENTAL
>>> + help
>>> + Support user namespaces. This allows containers, i.e.
>>> + vservers, to use user namespaces to provide different
>>> + user info for different servers. If unsure, say N.
>>> +
>>> config BLK_DEV_INITRD
>>> bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
>>> depends on BROKEN || !FRV
>
> The reason we removed these options earlier was a maintenance issue
> and the fact we could not actually compile out the namespaces.
I do not propose to compile out the namespaces, I just propose
to compile out the code that does the clone and release of new
namespaces. This is absolutely painless.
> If we don't cause maintenance complications I think the general
> idea is fine. But please. This all should show up under
> CONFIG_EMBEDDED since the only purpose is to save space.
Hm... Ok, but I also try to save the vmlinux size on my home
PC, so I'd be happy if I could just throw these things out.
Anyway - I will move the CONFIG_NAMESPACES to be selectable
with the EMBEDDED only.
> While things are experimental there is an additional purpose of
> not exposing people to broken or partially working code, so it
> does make sense to have an option there.
Ok, thanks.
So your accolades, can they be transformed into Acked-by-s or
just mentioned in the patch like "reviewed and approved by ..."?
> Eric
>
next prev parent reply other threads:[~2007-09-26 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 12:37 Playing with namespaces and bloat-o-meeter Pavel Emelyanov
[not found] ` <46FA528C.3000208-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-26 13:13 ` Serge E. Hallyn
[not found] ` <20070926131349.GA20637-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-09-26 13:17 ` Cedric Le Goater
[not found] ` <46FA5BF3.4030505-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-09-26 13:19 ` Cedric Le Goater
[not found] ` <46FA5C5C.2070906-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-09-26 13:20 ` Pavel Emelyanov
[not found] ` <46FA5C86.90201-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-26 13:23 ` Daniel Lezcano
2007-09-26 13:30 ` Serge E. Hallyn
2007-09-26 13:24 ` Cedric Le Goater
[not found] ` <46FA5D83.2010308-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-09-26 14:08 ` Pavel Emelyanov
2007-09-26 14:20 ` Pavel Emelyanov
[not found] ` <46FA6AC3.6090402-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-26 14:45 ` Eric W. Biederman
[not found] ` <m1y7etv634.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-09-26 14:49 ` Pavel Emelyanov [this message]
[not found] ` <46FA7186.1070202-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-09-26 15:42 ` 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=46FA7186.1070202@openvz.org \
--to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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