linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Suleiman Souhlal <ssouhlal@FreeBSD.org>
Cc: glommer@parallels.com, gthelen@google.com, yinghan@google.com,
	jbottomley@parallels.com, suleiman@google.com,
	linux-mm@kvack.org
Subject: Re: [RFC] [PATCH 0/4] memcg: Kernel memory accounting.
Date: Mon, 17 Oct 2011 09:32:57 +0900	[thread overview]
Message-ID: <20111017093257.054e9af6.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <1318639110-27714-1-git-send-email-ssouhlal@FreeBSD.org>

On Fri, 14 Oct 2011 17:38:26 -0700
Suleiman Souhlal <ssouhlal@FreeBSD.org> wrote:

> This patch series introduces kernel memory accounting to memcg.
> It currently only accounts for slab.
> 
> With this, kernel memory gets counted in a memcg's usage_in_bytes.
> 
> Slab gets accounted per-page, by using per-cgroup kmem_caches that
> get created the first time an allocation of that type is done by
> that cgroup.
> This means that we only have to do charges/uncharges in the slow
> path of the slab allocator, which should have low performance
> impacts.
> 
> A per-cgroup kmem_cache will appear in slabinfo named like its
> original cache, with the cgroup's name in parenthesis.
> On cgroup deletion, the accounting gets moved to the root cgroup
> and any existing cgroup kmem_cache gets "dead" appended to its
> name, to indicate that its accounting was migrated.
> 
> TODO:
> 	- Per-memcg slab shrinking (we have patches for that already).
> 	- Make it support the other slab allocators.
> 	- Come up with a scheme that does not require holding
> 	  rcu_read_lock in the whole slab allocation path.
> 	- Account for other types of kernel memory than slab.
> 	- Migrate to the parent cgroup instead of root on cgroup
> 	  deletion.
> 

Could you show rough perforamance score ?

For example,
Assume cgroup dir as

  /cgroup/memory <--- root
		|-A  memory.use_hierarchy=1   no limit
		  |-B                         no limit
1) Compare kernel make 'sys time' under root, A, B.
2) run unixbench under root, A, B.

I think you may have some numbers already.

Thanks,
-Kame








--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2011-10-17  0:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-15  0:38 Suleiman Souhlal
2011-10-15  0:38 ` [RFC] [PATCH 1/4] memcg: Kernel memory accounting infrastructure Suleiman Souhlal
2011-10-15  0:38   ` [RFC] [PATCH 2/4] memcg: Introduce __GFP_NOACCOUNT Suleiman Souhlal
2011-10-15  0:38     ` [RFC] [PATCH 3/4] memcg: Slab accounting Suleiman Souhlal
2011-10-15  0:38       ` [RFC] [PATCH 4/4] memcg: Document kernel memory accounting Suleiman Souhlal
2011-10-17  8:56         ` Glauber Costa
2011-10-17 17:19           ` Suleiman Souhlal
2011-10-17  0:32 ` KAMEZAWA Hiroyuki [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=20111017093257.054e9af6.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=glommer@parallels.com \
    --cc=gthelen@google.com \
    --cc=jbottomley@parallels.com \
    --cc=linux-mm@kvack.org \
    --cc=ssouhlal@FreeBSD.org \
    --cc=suleiman@google.com \
    --cc=yinghan@google.com \
    /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