Linux Container Development
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Dwight Schauer <dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: New LXC HOW-TO
Date: Sun, 18 Oct 2009 17:44:31 +0200	[thread overview]
Message-ID: <4ADB37DF.8050907@free.fr> (raw)
In-Reply-To: <68e6eac60910180710j6ebce156w886588013786b4e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Dwight Schauer wrote:
> I'm trying to get the needed LXC kernel config options into the default Arch
> Linux kernel package.
> http://bugs.archlinux.org/task/16715
>
> There is a concern about any potential drawbacks in enabling these options,
> especially for those that don't use Linux containers.
>
> Is anyone aware of any negative impact (apart from size maybe) of having
> these features being enabled? Especially for those not using these features?
>
> On Sat, Oct 17, 2009 at 7:32 PM, Dwight Schauer <dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>   
>> I just made it and it is somewhat archlinux specific, but others might find
>> it useful.
>>
>> http://lxc.teegra.net/
>>
>> --
>> Dwight
>>
>>
>>
>>
>>     
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>
>
>   
In general the cgroup adds a small overhead at fork/exit when a subsystem make use of the cgroup_callbacks, for example the freezer. But that can be considered as negligeable.

CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y

This one does not add any overhead.

CONFIG_CGROUP_DEVICE=y

For these ones, I don't know.

CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y

AFAIR these following options add some overhead especially the memory resource controller.

CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
CONFIG_MM_OWNER=y


The overhead and footprint of the following options are neligeable

CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_NET_CLS_CGROUP=y


This one, no overhead.
CONFIG_SECURITY_FILE_CAPABILITIES=y

  parent reply	other threads:[~2009-10-18 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  0:32 New LXC HOW-TO Dwight Schauer
     [not found] ` <68e6eac60910171732w6b7fe5dbt755963653e417302-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-18  8:24   ` Daniel Lezcano
2009-10-18 14:10   ` Dwight Schauer
     [not found]     ` <68e6eac60910180710j6ebce156w886588013786b4e9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-18 15:44       ` Daniel Lezcano [this message]
     [not found]         ` <4ADB37DF.8050907-GANU6spQydw@public.gmane.org>
2009-10-27  8:42           ` KAMEZAWA Hiroyuki
     [not found]             ` <20091027174225.ddd56319.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-10-27 10:15               ` Daniel Lezcano

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=4ADB37DF.8050907@free.fr \
    --to=daniel.lezcano-ganu6spqydw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=dschauer-Re5JQEeQqe8AvxtiuMwx3w@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