All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: KAMEZAWA Hiroyuki
	<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: New LXC HOW-TO
Date: Tue, 27 Oct 2009 11:15:26 +0100	[thread overview]
Message-ID: <4AE6C83E.1040407@free.fr> (raw)
In-Reply-To: <20091027174225.ddd56319.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>

KAMEZAWA Hiroyuki wrote:
> On Sun, 18 Oct 2009 17:44:31 +0200
> Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org> wrote:
>
>   
>> 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
>>
>>
>>     
> sorry, memcg's performance fix is now tested under -mm kernel.
> plz wait for 2.6.33 ;(
>   
Cool !

      parent reply	other threads:[~2009-10-27 10:15 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
     [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 [this message]

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=4AE6C83E.1040407@free.fr \
    --to=daniel.lezcano-ganu6spqydw@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@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.