OpenVZ Forum - RDF feed
type: channel
items: Playing with namespaces and bloat-o-meeter
items: Re: Playing with namespaces and bloat-o-meeter

Playing with namespaces and bloat-o-meeter
type: item
description: Hi, guys! I've noticed that compiling out all the core related to cloning and cleaning the new namespace saves us more than a Kbyte (!) from the vmlinux. add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) function old new delta copy_user_ns - 181 +181 copy_ipcs - 149 +149 copy_utsname - 120 +120 shm_exit_ns - 106 +106 sem_exit_ns - 106 +106 msg_exit_ns - 106 +106 freeary - 100 +100 release_uids - 95 +95 freeque - 92 +92 free_nsproxy 48 99 +51 __sem_init_ns - 45 +45 shm_init_ns - 42 +42 sem_init_ns - 42 +42 msg_init_ns - 42 +42 __shm_init_ns - 38 +38 create_new_namespaces 300 335 +35 __msg_init_ns - 31 +31 sysvipc_proc_release 5 35 +30 free_ipc_ns - 30 +30 do_shm_rmid - 29 +29 shm_release 18 39 +21 free_user_ns - 16 +16 sysvipc_proc_open 100 111 +11 do_shmat 778 787 +9 free_uts_ns - 5 +5 sys_shmctl 1934 1907 -27 msg_init 82 47 -35 shm_init 92 47 -45 sem_init 99 44 -55 sys_msgctl 1394 1311 -83 sys_semctl 2123 2032 -91 Since there already were some questions like "do I need it on my cellphone?" in reply to pid namespaces patches and so on, why don't we make ALL the namespaces cloning code under the config option to make those people happy? Here's the proposed patch. Signed-off-by: Pavel Emelyanov <xemul@openvz.org> --- diff --git a/include/linux/ipc.h b/include/linux/ipc.h index 96988d1..b882610 100644 --- a/include/linux/ipc.h +++ b/include/linux/ipc.h @@ -100,56 +100,6 @@ struct kern_ipc_perm void *security; }; -struct ipc_ids; -struct ipc_namespace { - struct kref kref; - struct ipc_ids *ids[3]; - - int sem_ctls[4]; - int used_sems; - - int msg_ctlmax; - int msg_ctlmnb; - int msg_ctlmni; - - size_t shm_ctlmax; - size_t shm_ctlall; - int shm_ctlmni; - int shm_tot; -}; - -extern struct ipc_namespace init_ipc_ns; - -#ifdef CONFIG_SYSVIPC -#define INIT_IPC_NS(ns) .ns = &init_ipc_ns, -extern void free_ipc_ns(struct kref *kref); -extern struct ipc_namespace *copy_ipcs(unsigned long flags, - struct ipc_namespace *ns); -#else -#define INIT_IPC_NS(ns) -static inline…
creator: Pavel Emelianov
date: 2007-09-26T12:37:32-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Quoting Pavel Emelyanov (xemul@openvz.org): > Hi, guys! > > I've noticed that compiling out all the core related to > cloning and cleaning the new namespace saves us more than > a Kbyte (!) from the vmlinux. > > add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) > function old new delta > copy_user_ns - 181 +181 > copy_ipcs - 149 +149 > copy_utsname - 120 +120 > shm_exit_ns - 106 +106 > sem_exit_ns - 106 +106 > msg_exit_ns - 106 +106 > freeary - 100 +100 > release_uids - 95 +95 > freeque - 92 +92 > free_nsproxy 48 99 +51 > __sem_init_ns - 45 +45 > shm_init_ns - 42 +42 > sem_init_ns - 42 +42 > msg_init_ns - 42 +42 > __shm_init_ns - 38 +38 > create_new_namespaces 300 335 +35 > __msg_init_ns - 31 +31 > sysvipc_proc_release 5 35 +30 > free_ipc_ns - 30 +30 > do_shm_rmid - 29 +29 > shm_release 18 39 +21 > free_user_ns - 16 +16 > sysvipc_proc_open 100 111 +11 > do_shmat 778 787 +9 > free_uts_ns - 5 +5 > sys_shmctl 1934 1907 -27 > msg_init 82 47 -35 > shm_init 92 47 -45 > sem_init 99 44 -55 > sys_msgctl 1394 1311 -83 > sys_semctl 2123 2032 -91 > > Since there already were some questions like "do I need it > on my cellphone?" in reply to pid namespaces patches and > so on, why don't we make ALL the namespaces cloning code > under the config option to make those people happy? > > Here's the proposed patch. How about a single config variable for all namespaces? -serge > Signed-off-by: Pavel Emelyanov <xemul@openvz.org> > > --- > > diff --git a/include/linux/ipc.h b/include/linux/ipc.h > index 96988d1..b882610 100644 > --- a/include/linux/ipc.h > +++ b/include/linux/ipc.h > @@ -100,56 +100,6 @@ struct kern_ipc_perm > void *security; > }; > > -struct ipc_ids; > -struct ipc_namespace { > - struct kref kref; > - struct ipc_ids *ids[3]; > - > - int sem_ctls[4]; > - int used_sems; > - > - int msg_ctlmax; > - int msg_ctlmnb; > - int msg_ctlmni; > - > - size_t shm_ctlmax; > - size_t shm_ctlall; > - int shm_ctlmni; > - int shm_tot; > -}; > - > -extern struct ipc_namespace init…
creator: serue
date: 2007-09-26T13:13:49-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Serge E. Hallyn wrote: > Quoting Pavel Emelyanov (xemul@openvz.org): >> Hi, guys! >> >> I've noticed that compiling out all the core related to >> cloning and cleaning the new namespace saves us more than >> a Kbyte (!) from the vmlinux. >> >> add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) >> function old new delta >> copy_user_ns - 181 +181 >> copy_ipcs - 149 +149 >> copy_utsname - 120 +120 >> shm_exit_ns - 106 +106 >> sem_exit_ns - 106 +106 >> msg_exit_ns - 106 +106 >> freeary - 100 +100 >> release_uids - 95 +95 >> freeque - 92 +92 >> free_nsproxy 48 99 +51 >> __sem_init_ns - 45 +45 >> shm_init_ns - 42 +42 >> sem_init_ns - 42 +42 >> msg_init_ns - 42 +42 >> __shm_init_ns - 38 +38 >> create_new_namespaces 300 335 +35 >> __msg_init_ns - 31 +31 >> sysvipc_proc_release 5 35 +30 >> free_ipc_ns - 30 +30 >> do_shm_rmid - 29 +29 >> shm_release 18 39 +21 >> free_user_ns - 16 +16 >> sysvipc_proc_open 100 111 +11 >> do_shmat 778 787 +9 >> free_uts_ns - 5 +5 >> sys_shmctl 1934 1907 -27 >> msg_init 82 47 -35 >> shm_init 92 47 -45 >> sem_init 99 44 -55 >> sys_msgctl 1394 1311 -83 >> sys_semctl 2123 2032 -91 >> >> Since there already were some questions like "do I need it >> on my cellphone?" in reply to pid namespaces patches and >> so on, why don't we make ALL the namespaces cloning code >> under the config option to make those people happy? >> >> Here's the proposed patch. > > How about a single config variable for all namespaces? yes good idea. C. _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Cedric Le Goater
date: 2007-09-26T13:17:39-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Cedric Le Goater wrote: > Serge E. Hallyn wrote: >> Quoting Pavel Emelyanov (xemul@openvz.org): >>> Hi, guys! >>> >>> I've noticed that compiling out all the core related to >>> cloning and cleaning the new namespace saves us more than >>> a Kbyte (!) from the vmlinux. >>> >>> add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) >>> function old new delta >>> copy_user_ns - 181 +181 >>> copy_ipcs - 149 +149 >>> copy_utsname - 120 +120 >>> shm_exit_ns - 106 +106 >>> sem_exit_ns - 106 +106 >>> msg_exit_ns - 106 +106 >>> freeary - 100 +100 >>> release_uids - 95 +95 >>> freeque - 92 +92 >>> free_nsproxy 48 99 +51 >>> __sem_init_ns - 45 +45 >>> shm_init_ns - 42 +42 >>> sem_init_ns - 42 +42 >>> msg_init_ns - 42 +42 >>> __shm_init_ns - 38 +38 >>> create_new_namespaces 300 335 +35 >>> __msg_init_ns - 31 +31 >>> sysvipc_proc_release 5 35 +30 >>> free_ipc_ns - 30 +30 >>> do_shm_rmid - 29 +29 >>> shm_release 18 39 +21 >>> free_user_ns - 16 +16 >>> sysvipc_proc_open 100 111 +11 >>> do_shmat 778 787 +9 >>> free_uts_ns - 5 +5 >>> sys_shmctl 1934 1907 -27 >>> msg_init 82 47 -35 >>> shm_init 92 47 -45 >>> sem_init 99 44 -55 >>> sys_msgctl 1394 1311 -83 >>> sys_semctl 2123 2032 -91 >>> >>> Since there already were some questions like "do I need it >>> on my cellphone?" in reply to pid namespaces patches and >>> so on, why don't we make ALL the namespaces cloning code >>> under the config option to make those people happy? >>> >>> Here's the proposed patch. >> How about a single config variable for all namespaces? > > yes good idea. oops, that done already in the patch : CONFIG_NAMESPACES thanks :) C. _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Cedric Le Goater
date: 2007-09-26T13:19:24-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Cedric Le Goater wrote: > Cedric Le Goater wrote: >> Serge E. Hallyn wrote: >>> Quoting Pavel Emelyanov (xemul@openvz.org): >>>> Hi, guys! >>>> >>>> I've noticed that compiling out all the core related to >>>> cloning and cleaning the new namespace saves us more than >>>> a Kbyte (!) from the vmlinux. >>>> >>>> add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) >>>> function old new delta >>>> copy_user_ns - 181 +181 >>>> copy_ipcs - 149 +149 >>>> copy_utsname - 120 +120 >>>> shm_exit_ns - 106 +106 >>>> sem_exit_ns - 106 +106 >>>> msg_exit_ns - 106 +106 >>>> freeary - 100 +100 >>>> release_uids - 95 +95 >>>> freeque - 92 +92 >>>> free_nsproxy 48 99 +51 >>>> __sem_init_ns - 45 +45 >>>> shm_init_ns - 42 +42 >>>> sem_init_ns - 42 +42 >>>> msg_init_ns - 42 +42 >>>> __shm_init_ns - 38 +38 >>>> create_new_namespaces 300 335 +35 >>>> __msg_init_ns - 31 +31 >>>> sysvipc_proc_release 5 35 +30 >>>> free_ipc_ns - 30 +30 >>>> do_shm_rmid - 29 +29 >>>> shm_release 18 39 +21 >>>> free_user_ns - 16 +16 >>>> sysvipc_proc_open 100 111 +11 >>>> do_shmat 778 787 +9 >>>> free_uts_ns - 5 +5 >>>> sys_shmctl 1934 1907 -27 >>>> msg_init 82 47 -35 >>>> shm_init 92 47 -45 >>>> sem_init 99 44 -55 >>>> sys_msgctl 1394 1311 -83 >>>> sys_semctl 2123 2032 -91 >>>> >>>> Since there already were some questions like "do I need it >>>> on my cellphone?" in reply to pid namespaces patches and >>>> so on, why don't we make ALL the namespaces cloning code >>>> under the config option to make those people happy? >>>> >>>> Here's the proposed patch. >>> How about a single config variable for all namespaces? >> yes good idea. > > > oops, that done already in the patch : CONFIG_NAMESPACES So... Acked-by: Serge E. Hallyn and Cedric Le Goater ? :) > thanks :) > > C. > > _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: Pavel Emelianov
date: 2007-09-26T13:20:06-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Pavel Emelyanov wrote: > Cedric Le Goater wrote: >> Cedric Le Goater wrote: >>> Serge E. Hallyn wrote: >>>> Quoting Pavel Emelyanov (xemul@openvz.org): >>>>> Hi, guys! >>>>> >>>>> I've noticed that compiling out all the core related to >>>>> cloning and cleaning the new namespace saves us more than >>>>> a Kbyte (!) from the vmlinux. >>>>> >>>>> add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) >>>>> function old new delta >>>>> copy_user_ns - 181 +181 >>>>> copy_ipcs - 149 +149 >>>>> copy_utsname - 120 +120 >>>>> shm_exit_ns - 106 +106 >>>>> sem_exit_ns - 106 +106 >>>>> msg_exit_ns - 106 +106 >>>>> freeary - 100 +100 >>>>> release_uids - 95 +95 >>>>> freeque - 92 +92 >>>>> free_nsproxy 48 99 +51 >>>>> __sem_init_ns - 45 +45 >>>>> shm_init_ns - 42 +42 >>>>> sem_init_ns - 42 +42 >>>>> msg_init_ns - 42 +42 >>>>> __shm_init_ns - 38 +38 >>>>> create_new_namespaces 300 335 +35 >>>>> __msg_init_ns - 31 +31 >>>>> sysvipc_proc_release 5 35 +30 >>>>> free_ipc_ns - 30 +30 >>>>> do_shm_rmid - 29 +29 >>>>> shm_release 18 39 +21 >>>>> free_user_ns - 16 +16 >>>>> sysvipc_proc_open 100 111 +11 >>>>> do_shmat 778 787 +9 >>>>> free_uts_ns - 5 +5 >>>>> sys_shmctl 1934 1907 -27 >>>>> msg_init 82 47 -35 >>>>> shm_init 92 47 -45 >>>>> sem_init 99 44 -55 >>>>> sys_msgctl 1394 1311 -83 >>>>> sys_semctl 2123 2032 -91 >>>>> >>>>> Since there already were some questions like "do I need it >>>>> on my cellphone?" in reply to pid namespaces patches and >>>>> so on, why don't we make ALL the namespaces cloning code >>>>> under the config option to make those people happy? >>>>> >>>>> Here's the proposed patch. >>>> How about a single config variable for all namespaces? >>> yes good idea. >> >> oops, that done already in the patch : CONFIG_NAMESPACES > > So... Acked-by: Serge E. Hallyn and Cedric Le Goater ? :) That is a good idea, that will avoid to have the namespaces config all around the menuconfig too. _______________________________________________ Containers mailing list Contain…
creator: Daniel Lezcano
date: 2007-09-26T13:23:57-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Pavel Emelyanov wrote: > Hi, guys! > > I've noticed that compiling out all the core related to > cloning and cleaning the new namespace saves us more than > a Kbyte (!) from the vmlinux. cool. but compared to the 5KB pid ns is adding, it's not much. I guess anything that can be saved is good to save when you run on a cell. > add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) > function old new delta > copy_user_ns - 181 +181 > copy_ipcs - 149 +149 > copy_utsname - 120 +120 > shm_exit_ns - 106 +106 > sem_exit_ns - 106 +106 > msg_exit_ns - 106 +106 > freeary - 100 +100 > release_uids - 95 +95 > freeque - 92 +92 > free_nsproxy 48 99 +51 > __sem_init_ns - 45 +45 > shm_init_ns - 42 +42 > sem_init_ns - 42 +42 > msg_init_ns - 42 +42 > __shm_init_ns - 38 +38 > create_new_namespaces 300 335 +35 > __msg_init_ns - 31 +31 > sysvipc_proc_release 5 35 +30 > free_ipc_ns - 30 +30 > do_shm_rmid - 29 +29 > shm_release 18 39 +21 > free_user_ns - 16 +16 > sysvipc_proc_open 100 111 +11 > do_shmat 778 787 +9 > free_uts_ns - 5 +5 > sys_shmctl 1934 1907 -27 > msg_init 82 47 -35 > shm_init 92 47 -45 > sem_init 99 44 -55 > sys_msgctl 1394 1311 -83 > sys_semctl 2123 2032 -91 > > Since there already were some questions like "do I need it > on my cellphone?" in reply to pid namespaces patches and > so on, why don't we make ALL the namespaces cloning code > under the config option to make those people happy? > > Here's the proposed patch. I think I'm ok with it but it would be easier to review if you could split it in little patchlets, at least one for each namespace. diffstats are welcome also :) > Signed-off-by: Pavel Emelyanov <xemul@openvz.org> > > --- > > diff --git a/include/linux/ipc.h b/include/linux/ipc.h > index 96988d1..b882610 100644 > --- a/include/linux/ipc.h > +++ b/include/linux/ipc.h > @@ -100,56 +100,6 @@ struct kern_ipc_perm > void *security; > }; > > -struct ipc_ids; > -struct ipc_namespace { > - struct kref kref; > - struct ipc_ids *ids[3]; > - > - int sem_ctls[4]; …
creator: Cedric Le Goater
date: 2007-09-26T13:24:19-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Quoting Cedric Le Goater (clg@fr.ibm.com): > Cedric Le Goater wrote: > > Serge E. Hallyn wrote: > >> Quoting Pavel Emelyanov (xemul@openvz.org): > >>> Hi, guys! > >>> > >>> I've noticed that compiling out all the core related to > >>> cloning and cleaning the new namespace saves us more than > >>> a Kbyte (!) from the vmlinux. > >>> > >>> add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) > >>> function old new delta > >>> copy_user_ns - 181 +181 > >>> copy_ipcs - 149 +149 > >>> copy_utsname - 120 +120 > >>> shm_exit_ns - 106 +106 > >>> sem_exit_ns - 106 +106 > >>> msg_exit_ns - 106 +106 > >>> freeary - 100 +100 > >>> release_uids - 95 +95 > >>> freeque - 92 +92 > >>> free_nsproxy 48 99 +51 > >>> __sem_init_ns - 45 +45 > >>> shm_init_ns - 42 +42 > >>> sem_init_ns - 42 +42 > >>> msg_init_ns - 42 +42 > >>> __shm_init_ns - 38 +38 > >>> create_new_namespaces 300 335 +35 > >>> __msg_init_ns - 31 +31 > >>> sysvipc_proc_release 5 35 +30 > >>> free_ipc_ns - 30 +30 > >>> do_shm_rmid - 29 +29 > >>> shm_release 18 39 +21 > >>> free_user_ns - 16 +16 > >>> sysvipc_proc_open 100 111 +11 > >>> do_shmat 778 787 +9 > >>> free_uts_ns - 5 +5 > >>> sys_shmctl 1934 1907 -27 > >>> msg_init 82 47 -35 > >>> shm_init 92 47 -45 > >>> sem_init 99 44 -55 > >>> sys_msgctl 1394 1311 -83 > >>> sys_semctl 2123 2032 -91 > >>> > >>> Since there already were some questions like "do I need it > >>> on my cellphone?" in reply to pid namespaces patches and > >>> so on, why don't we make ALL the namespaces cloning code > >>> under the config option to make those people happy? > >>> > >>> Here's the proposed patch. > >> How about a single config variable for all namespaces? > > > > yes good idea. > > > oops, that done already in the patch : CONFIG_NAMESPACES > > thanks :) That at least organizes them all in Kconfig. I meant one config variable, period. Then instead of adding CONFIG_USER_NS and such whlie they are experimental, put all experimental namespaces (i.e. maybe soon user and network) und…
creator: serue
date: 2007-09-26T13:30:19-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Cedric Le Goater wrote: > Pavel Emelyanov wrote: >> Hi, guys! >> >> I've noticed that compiling out all the core related to >> cloning and cleaning the new namespace saves us more than >> a Kbyte (!) from the vmlinux. > > cool. > > but compared to the 5KB pid ns is adding, it's not much. I guess > anything that can be saved is good to save when you run on a cell. Yup, but I've already sent 3 patches to Andrew that save 1.5 KB so we have already managed to get a half for cell users ;) >> add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) >> function old new delta >> copy_user_ns - 181 +181 >> copy_ipcs - 149 +149 >> copy_utsname - 120 +120 >> shm_exit_ns - 106 +106 >> sem_exit_ns - 106 +106 >> msg_exit_ns - 106 +106 >> freeary - 100 +100 >> release_uids - 95 +95 >> freeque - 92 +92 >> free_nsproxy 48 99 +51 >> __sem_init_ns - 45 +45 >> shm_init_ns - 42 +42 >> sem_init_ns - 42 +42 >> msg_init_ns - 42 +42 >> __shm_init_ns - 38 +38 >> create_new_namespaces 300 335 +35 >> __msg_init_ns - 31 +31 >> sysvipc_proc_release 5 35 +30 >> free_ipc_ns - 30 +30 >> do_shm_rmid - 29 +29 >> shm_release 18 39 +21 >> free_user_ns - 16 +16 >> sysvipc_proc_open 100 111 +11 >> do_shmat 778 787 +9 >> free_uts_ns - 5 +5 >> sys_shmctl 1934 1907 -27 >> msg_init 82 47 -35 >> shm_init 92 47 -45 >> sem_init 99 44 -55 >> sys_msgctl 1394 1311 -83 >> sys_semctl 2123 2032 -91 >> >> Since there already were some questions like "do I need it >> on my cellphone?" in reply to pid namespaces patches and >> so on, why don't we make ALL the namespaces cloning code >> under the config option to make those people happy? >> >> Here's the proposed patch. > > I think I'm ok with it but it would be easier to review if you > could split it in little patchlets, at least one for each > namespace. diffstats are welcome also :) > >> Signed-off-by: Pavel Emelyanov <xemul@openvz.org> >> >> --- >> >> diff --git a/include/linux/ipc.h b/include/linux/ipc.h >> index 96988d1..b882610 100644 >> --- a/include/linux/ip…
creator: Pavel Emelianov
date: 2007-09-26T14:08:11-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Pavel Emelyanov wrote: > Hi, guys! > > I've noticed that compiling out all the core related to > cloning and cleaning the new namespace saves us more than > a Kbyte (!) from the vmlinux. Sorry guys, this patch is a bit broken :P CONFIG_NS_PID is used in kernel/pid.c while the real option is CONFIG_NS_PIDS :( I've remade the patch and it actually saves 2KB :) I will send it to Andrew soon. add/remove: 27/0 grow/shrink: 11/7 up/down: 2477/-340 (2137) function old new delta copy_pid_ns - 537 +537 copy_user_ns - 181 +181 copy_ipcs - 149 +149 zap_pid_ns_processes - 130 +130 copy_utsname - 120 +120 shm_exit_ns - 106 +106 sem_exit_ns - 106 +106 msg_exit_ns - 106 +106 freeary - 100 +100 release_uids - 95 +95 freeque - 92 +92 free_nsproxy 48 123 +75 create_new_namespaces 300 358 +58 free_pid_ns - 56 +56 pid_namespaces_init - 48 +48 __sem_init_ns - 45 +45 shm_init_ns - 42 +42 sem_init_ns - 42 +42 msg_init_ns - 42 +42 __shm_init_ns - 38 +38 __msg_init_ns - 31 +31 sysvipc_proc_release 5 35 +30 proc_kill_sb 5 35 +30 free_ipc_ns - 30 +30 do_shm_rmid - 29 +29 proc_set_super 13 38 +25 shm_release 18 39 +21 put_pid 75 95 +20 alloc_pid 687 706 +19 pid_caches_mutex - 16 +16 free_user_ns - 16 +16 sysvipc_proc_open 100 111 +11 do_shmat 778 787 +9 pid_caches_lh - 8 +8 free_uts_ns - 5 +5 pid_ns_cachep - 4 +4 __initcall_pid_namespaces_init6 - 4 +4 do_exit 1855 1856 +1 show_stat 1665 1661 -4 sys_shmctl 1934 1907 -27 msg_init 82 47 -35 shm_init 92 47 -45 sem_init 99 44 -55 sys_msgctl 1394 1311 -83 sys_semctl 2123 2032 -91 > add/remove: 19/0 grow/shrink: 6/6 up/down: 1532/-336 (1196) > function old new delta > copy_user_ns - 181 +181 > copy_ipcs - 149 +149 > copy_utsname - 120 +120 > shm_exit_ns - 106 +106 > sem_exit_ns - 106 +106 > msg_exit_ns - 106 +106 > freeary - 100 +100 > release_uids - 95 +95 > freeque - 92 +92 > free_nsproxy 48 99 +51 > __sem_init_ns - 45 +45 > shm_init_ns - 42 +42 > sem_init_ns - 42 +42 > msg_init_ns - 42 +42 > __shm_init_ns - 38 +38 > create_new_namespaces 300 335 +…
creator: Pavel Emelianov
date: 2007-09-26T14:20:51-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Pavel Emelyanov <xemul@openvz.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. 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. 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. Eric _______________________________________________ Containers mailing list Containers@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/containers
creator: ebiederm
date: 2007-09-26T14:45:03-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Eric W. Biederman wrote: > Pavel Emelyanov <xemul@openvz.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 the…
creator: Pavel Emelianov
date: 2007-09-26T14:49:42-00:00

Re: Playing with namespaces and bloat-o-meeter
type: item
description: Quoting Pavel Emelyanov (xemul@openvz.org): > Eric W. Biederman wrote: > > Pavel Emelyanov <xemul@openvz.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 additi…
creator: serue
date: 2007-09-26T15:42:36-00:00