All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	"Eric W. Biederman"
	<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: Playing with namespaces and bloat-o-meeter
Date: Wed, 26 Sep 2007 17:20:06 +0400	[thread overview]
Message-ID: <46FA5C86.90201@openvz.org> (raw)
In-Reply-To: <46FA5C5C.2070906-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>

Cedric Le Goater wrote:
> Cedric Le Goater wrote:
>> Serge E. Hallyn wrote:
>>> Quoting Pavel Emelyanov (xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.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.
> 
> 

  parent reply	other threads:[~2007-09-26 13:20 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 [this message]
     [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
     [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=46FA5C86.90201@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 \
    /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.