lkml.org 
[lkml]   [2008]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: why are namespaces required?
On Fri, 8 Aug 2008, Andi Kleen wrote:

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

from a size point of view the namespace options may not have much impact,
but what about performance? supporting namespaces requires additional
checking each time something is accessed (not to mention new codepaths).

how about consolodating all the namespace items under a single namespace
menu item so that they can all be disabled with one click, but people who
want fine-grained control over the different portions can still have it.

but (going back to my initial post) namespaces should not be forced on for
!embeded (or if they are then the options to disable namespaces should be
moved inside the embeded menu)

David Lang


\
 
 \ /
  Last update: 2008-08-08 17:09    [W:0.106 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site