From: Andi Kleen <andi@firstfloor.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: david@lang.hm, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: why are namespaces required?
Date: Fri, 08 Aug 2008 13:29:06 +0200 [thread overview]
Message-ID: <87ej4z4uf1.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080808013304.GA27778@martell.zuzino.mipt.ru> (Alexey Dobriyan's message of "Fri, 8 Aug 2008 05:33:04 +0400")
Alexey Dobriyan <adobriyan@gmail.com> writes:
>
> And while we're at it, data from my usual config adding _NS options
> one-by-one.
>
> $ size vmlinux-000 vmlinux-uts-ns vmlinux-ipc-ns vmlinux-user-ns vmlinux-pid-ns
> text data bss dec hex filename
> 2560804 217296 225280 3003380 2dd3f4 vmlinux-000
> 2560948 217296 225280 3003524 2dd484 vmlinux-uts-ns (+144)
> 2561452 217296 225280 3004028 2dd67c vmlinux-ipc-ns (+504)
> 2561805 217296 225280 3004381 2dd7dd vmlinux-user-ns (+353)
> 2562819 217300 225280 3005399 2ddbd7 vmlinux-pid-ns (+1018)
>
> What amazing .text savings we have here.
Fully agreed. Probably a lot of these CONFIG options should be just dropped.
They are quite user unfriendly with very little gain.
It seems like there is unbounded growth in different name space options
which also implies unbounded CONFIG growth. At least they should be all
consolidated into a single CONFIG.
-Andi
next prev parent reply other threads:[~2008-08-08 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 0:54 why are namespaces required? david
2008-08-08 1:11 ` david
2008-08-08 1:33 ` Alexey Dobriyan
2008-08-08 11:29 ` Andi Kleen [this message]
2008-08-08 15:08 ` david
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=87ej4z4uf1.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=adobriyan@gmail.com \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.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.