From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH 0/6] memcg update v6 (for review and discuss)
Date: Tue, 7 Oct 2008 10:22:48 +0900 [thread overview]
Message-ID: <20081007102248.0f1694b8.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <48EA4A3C.3030106@linux.vnet.ibm.com>
On Mon, 06 Oct 2008 22:56:20 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> KAMEZAWA Hiroyuki wrote:
> > On Wed, 1 Oct 2008 16:52:33 +0900
> > KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> >
> >> This series is update from v5.
> >>
> >> easy 4 patches are already posted as ready-to-go-series.
> >>
> >> This is need-more-discuss set.
> >>
> >> Includes following 6 patches. (reduced from v5).
> >> The whole series are reordered.
> >>
> >> [1/6] make page_cgroup->flags to be atomic.
> >> [2/6] allocate all page_cgroup at boot.
> >> [3/6] rewrite charge path by charge/commit/cancel
> >> [4/6] new force_empty and move_account
> >> [5/6] lazy lru free
> >> [6/6] lazy lru add.
> >>
> >> Patch [3/6] and [4/6] are totally rewritten.
> >> Races in Patch [6/6] is fixed....I think.
> >>
> >> Patch [1-4] seems to be big but there is no complicated ops.
> >> Patch [5-6] is more racy. Check-by-regression-test is necessary.
> >> (Of course, I does some.)
> >>
> >> If ready-to-go-series goes, next is patch 1 and 2.
> >>
> >
> > No terrible bugs until now on my test.
> >
> > My current idea for next week is following.
> > (I may have to wait until the end of next merge window. If so,
> > I'll wait and maintain this set.)
> >
> > - post ready-to-go set again.
> > - post 1/6 and 2/6 as may-ready-to-go set. I don't chagnge order of these.
> > - reflects comments for 3/6.
> > patch 3/6 adds new functions. So, please tell me if you have better idea
> > about new functions.
> > - check logic for 4/6.
> > - 5/6 and 6/6 may need some more comments in codes.
> > - no new additional ones.
>
> Kamezawa-San, Andrew,
>
> I think patches 1 and 2 are ready to go. Andrew they remove the cgroup member
> from struct page and will help reduce the overhead for distros that care about
> 32 bit systems and also help with performance (in my runs so far).
>
> I would recommend pushing 1 and 2 right away to -mm followed by the other
> performance improvements. Comments?
>
>
I'll rebase ready-to-go 4 patches and this 1 and 2 onto the latest mmotm
and send again.
Thank you for review.
Regards,
-Kame
> --
> Balbir
>
--
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
--
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>
prev parent reply other threads:[~2008-10-07 1:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 7:52 KAMEZAWA Hiroyuki
2008-10-01 7:55 ` [PATCH 1/6] atomic page_cgroup flags KAMEZAWA Hiroyuki
2008-10-06 7:42 ` Balbir Singh
2008-10-01 7:56 ` [PATCH 2/6] memcg: allocate page_cgroup at boot KAMEZAWA Hiroyuki
2008-10-02 8:49 ` [PATCH 2/6] memcg: allocate page_cgroup at boot (hunk fix) KAMEZAWA Hiroyuki
2008-10-06 16:32 ` Balbir Singh
2008-10-06 10:11 ` [PATCH 2/6] memcg: allocate page_cgroup at boot Balbir Singh
2008-10-01 7:57 ` [PATCH 3/6] memcg: charge-commit-cancel protocl KAMEZAWA Hiroyuki
2008-10-01 8:33 ` Daisuke Nishimura
2008-10-01 10:04 ` kamezawa.hiroyu
2008-10-03 10:05 ` Daisuke Nishimura
2008-10-03 15:15 ` kamezawa.hiroyu
2008-10-03 15:25 ` Daisuke Nishimura
2008-10-08 9:05 ` [RFC] memcg: handle migration by charge-commit-cancel (was " KAMEZAWA Hiroyuki
2008-10-01 7:59 ` [PATCH 4/6] memcg: new force_empty and move_account KAMEZAWA Hiroyuki
2008-10-01 16:38 ` Randy Dunlap
2008-10-02 5:13 ` KAMEZAWA Hiroyuki
2008-10-01 8:00 ` [PATCH 5/6] memcg: lazy lru freeing KAMEZAWA Hiroyuki
2008-10-09 5:39 ` Daisuke Nishimura
2008-10-09 6:26 ` KAMEZAWA Hiroyuki
2008-10-01 8:01 ` [PATCH 6/6] memcg: lazy lru addition KAMEZAWA Hiroyuki
2008-10-09 6:21 ` Daisuke Nishimura
2008-10-09 6:51 ` KAMEZAWA Hiroyuki
2008-10-02 9:02 ` [PATCH 0/6] memcg update v6 (for review and discuss) KAMEZAWA Hiroyuki
2008-10-06 17:26 ` Balbir Singh
2008-10-07 1:22 ` 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=20081007102248.0f1694b8.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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