linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	vgoyal@redhat.com, m-ikeda@ds.jp.nec.com, gthelen@google.com,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -mm 0/5] towards I/O aware memory cgroup v3.
Date: Tue, 3 Aug 2010 08:06:48 +0530	[thread overview]
Message-ID: <20100803023648.GB3863@balbir.in.ibm.com> (raw)
In-Reply-To: <20100802191113.05c982e4.kamezawa.hiroyu@jp.fujitsu.com>

* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2010-08-02 19:11:13]:

> 
> This is v3. removed terrble garbages from v2 and tested.(no big changes)
> 
> Now, it's merge-window and I'll have to maintain this in my box for a while.
> I'll continue to update this. Maybe we can make new progress after LinuxCon.
> (And I'll be busy for a while.)
>


I was catching up with my inbox, did not realize you had moved onto v3
and hence reviewed v1 first.
 
> This set has 2+1 purposes.
>  1. re-desgin struct page_cgroup and makes room for blocckio-cgroup ID.
>  2. implement quick updating method for memcg's file stat.
>  3. optionally? use spin_lock instead of bit_spinlock.
> 
> Plans after this.
> 
>  1. check influence of Mel's new writeback method.
>     I think we'll see OOM easier. IIUC, memory cgroup needs a thread like kswapd
>     to do background writeback or low-high watermark.
>     (By this, we can control priority of background writeout thread priority
>      by CFS. This is very good.)

Agreed, background watermark based reclaim is something we should look
at.

> 
>  2. implementing dirty_ratio.
>     Now, Greg Thelen is working on. One of biggest problems of previous trial was
>     update cost of status. I think this patch set can reduce it.

That is good news

> 
>  3. record blockio cgroup's ID.
>     Ikeda posted one. IIUC, it requires some consideration on (swapin)readahead
>     for assigning IDs. But it seemed to be good in general.
> 
> Importance is in this order in my mind. But all aboves can be done in parallel.
> 
> Beyond that, some guys has problem with file-cache-control. If it need to use
> account migration, we have to take care of races.
> 

-- 
	Three Cheers,
	Balbir

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2010-08-03  2:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 10:11 KAMEZAWA Hiroyuki
2010-08-02 10:13 ` [PATCH -mm 1/5] quick lookup memcg by ID KAMEZAWA Hiroyuki
2010-08-03  3:22   ` Balbir Singh
2010-08-03  3:21     ` KAMEZAWA Hiroyuki
2010-08-03  3:38       ` Balbir Singh
2010-08-03  4:31   ` Daisuke Nishimura
2010-08-03  4:37     ` KAMEZAWA Hiroyuki
2010-08-03  4:51       ` Daisuke Nishimura
2010-08-03  4:54         ` KAMEZAWA Hiroyuki
2010-08-03  5:04           ` Daisuke Nishimura
2010-08-02 10:14 ` [PATCH -mm 2/5] use ID in page cgroup KAMEZAWA Hiroyuki
2010-08-03  3:45   ` Balbir Singh
2010-08-03  3:48     ` KAMEZAWA Hiroyuki
2010-08-02 10:15 ` [PATCH -mm 3/5] memcg scalable file stat accounting method KAMEZAWA Hiroyuki
2010-08-03  3:33   ` Balbir Singh
2010-08-03  3:39     ` KAMEZAWA Hiroyuki
2010-08-04  0:55   ` Daisuke Nishimura
2010-08-04  1:11     ` KAMEZAWA Hiroyuki
2010-08-04  1:25       ` Daisuke Nishimura
2010-08-02 10:17 ` [PATCH -mm 4/5] memcg generic file stat accounting interface KAMEZAWA Hiroyuki
2010-08-03  4:03   ` Balbir Singh
2010-08-03  4:24     ` KAMEZAWA Hiroyuki
2010-08-02 10:20 ` [PATCH -mm 5/5] memcg: use spinlock in page_cgroup instead of bit_spinlock KAMEZAWA Hiroyuki
2010-08-03  4:06   ` Balbir Singh
2010-08-03  4:25     ` KAMEZAWA Hiroyuki
2010-08-03  2:36 ` Balbir Singh [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=20100803023648.GB3863@balbir.in.ibm.com \
    --to=balbir@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gthelen@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m-ikeda@ds.jp.nec.com \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=vgoyal@redhat.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