All of lore.kernel.org
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
To: Zhu Yanhai <zhu.yanhai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Han Ying <yinghan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: What's the progress of per cgroup background reclaim?
Date: Wed, 14 Mar 2012 17:32:09 +0900	[thread overview]
Message-ID: <4F605789.7070007@jp.fujitsu.com> (raw)
In-Reply-To: <CAC8teKW9Yry114+B06XiFbOtamwS6fNLzrKYo8PZazjEzMCiNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

(2012/03/14 16:53), Zhu Yanhai wrote:

> Hi all,
> Just a quick question, could you please tell me what's the current
> status of the development of per cgroup background reclaim? This topic
> seems to be silent after Han Ying's patchset V7
> (http://lwn.net/Articles/440073/) and Kame's async reclaim patchset V3
> (https://lkml.org/lkml/2011/5/26/20), and I can't find it in
> memcg-devel tree either.
> Is anyone still working on this?


I'll do and have a plan. But there are several ongoing projects as

 a) per lruvec lock
 b) page cgroup diet
 c) kmem accounting
 d) hugetlb accounting
 e) some fixes in cgroup
 f) more tweaks in vmscan.c
 g) writeback and dirty ratio.

I think it will come after a) and b), at least. And it's better
to have g) before kswapd-for-memcg.


Thanks,
-Kame

  parent reply	other threads:[~2012-03-14  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  7:53 What's the progress of per cgroup background reclaim? Zhu Yanhai
     [not found] ` <CAC8teKW9Yry114+B06XiFbOtamwS6fNLzrKYo8PZazjEzMCiNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-14  8:32   ` KAMEZAWA Hiroyuki [this message]
2012-03-14 16:17   ` Ying Han
     [not found]     ` <CALWz4iyqyQD3g27J=wLvQ=WN0enXLB3rmHDAb51UJaLPJDz5BA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-15  1:09       ` KAMEZAWA Hiroyuki
2012-03-15  3:12       ` Zhu Yanhai
     [not found]         ` <CAC8teKUrJ_ufkhtVAnsv-gzHfYmp8agY_bncOYS7mEdiqD+YZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-15 16:31           ` Ying Han
     [not found]             ` <CALWz4iwO+eGFW23qVwjy=MKufRtiVck08pJphSij226pjTQiBw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-19  8:09               ` Zhu Yanhai

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=4F605789.7070007@jp.fujitsu.com \
    --to=kamezawa.hiroyu-+cum20s59erqfuhtdcdx3a@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yinghan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=zhu.yanhai-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 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.