mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp, LKML <linux-kernel@vger.kernel.org>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>,
	ryov@valinux.co.jp
Subject: Re: [PATCH -mm][preview] memcg: a patch series for next [0/9]
Date: Tue, 19 Aug 2008 18:11:50 +0900	[thread overview]
Message-ID: <20080819181150.3a84f5dd.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20080819173014.17358c17.kamezawa.hiroyu@jp.fujitsu.com>

On Tue, 19 Aug 2008 17:30:14 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Hi, 
> 
> This post is for showing what I'm trying now.
> 
> This patch set is for memory resource controller.
> 4 purposes here.
>   - improve performance of memcg.
>   - remove lock_page_cgroup()
>   - making page_cgroup->flags to be atomic_ops.
>   - support mem+swap controller.
> 

Thank you for working on mem+swap controller.

I'll review and comment later.


Thanks,
Daisuke Nishimura.

> But this is still under test and the series is not well organised.
> and base tree is old. (2.6.27-rc1-mm1) I'll rebase this set to newer mmtom tree.
> 
> Maybe this set have some troubles/objections but I think the direction is not bad.
> 
> Patch description. (patch ordering is bad. I'll fix in the next post.)
> 
> [1/9] ... private_counter ...replace res_counter with my own counter.
>           This is for supporting mem+swap controller.
>           (And I think memcg has a bit different characteristics from other
>            users of res_counter....)
> 
> [2/9] ... change-order-uncharge ...
>           This patch is for making it easy to handle swap-cache.
> 
> [3/9] ... atomic_flags
>           This patch changes operations for page_cgroup->flags to be atomic_ops.
> 
> [4/9] ... delayed freeing.
>           delaying to free page_cgroup at uncharge.
> 
> [5/9] ... RCU freeing of page_cgroup
>           free page_cgroup by RCU.
> 
> [6/9] ... lockress page cgroup.
>           remove lock_page_cgroup() and use RCU semantics.
> 
> [7/9] ... add preftech
>           add prefetch() macro
> 
> [8/9] ... mem+swap controller base.
>           introduce mem+swap controller. A bit big patch....but have tons of TODO.
>           and have troubles. (it seems it's difficult to cause OOM killer.)
> 
> [9/9] ... mem+swap controller control files.
>           add mem+swap controller's control files.
> 
> I'd like to push patch [2,3,4,5,6,7] first.
> 
> Thanks,
> -Kame
> 

  parent reply	other threads:[~2008-08-19  9:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19  8:30 KAMEZAWA Hiroyuki
2008-08-19  8:37 ` [PATCH -mm][preview] memcg: a patch series for next [1/9] KAMEZAWA Hiroyuki
2008-08-19  8:38   ` [PATCH -mm][preview] memcg: a patch series for next [2/9] KAMEZAWA Hiroyuki
2008-08-19  8:39   ` [PATCH -mm][preview] memcg: a patch series for next [3/9] KAMEZAWA Hiroyuki
2008-08-19  8:40   ` [PATCH -mm][preview] memcg: a patch series for next [4/9] KAMEZAWA Hiroyuki
2008-08-19  8:41   ` [PATCH -mm][preview] memcg: a patch series for next [5/9] KAMEZAWA Hiroyuki
2008-08-19  8:42   ` [PATCH -mm][preview] memcg: a patch series for next [6/9] KAMEZAWA Hiroyuki
2008-08-19  8:43   ` [PATCH -mm][preview] memcg: a patch series for next [7/9] KAMEZAWA Hiroyuki
2008-08-19  8:44   ` [PATCH -mm][preview] memcg: a patch series for next [8/9] KAMEZAWA Hiroyuki
2008-08-22 10:29     ` Daisuke Nishimura
2008-08-22 11:54       ` KAMEZAWA Hiroyuki
2008-08-19  8:44   ` [PATCH -mm][preview] memcg: a patch series for next [9/9] KAMEZAWA Hiroyuki
2008-08-19  9:11 ` Daisuke Nishimura [this message]
2008-08-20  1:26   ` [PATCH -mm][preview] memcg: a patch series for next [0/9] KAMEZAWA Hiroyuki
2008-08-20  3:30 ` Balbir Singh
2008-08-20  3:51   ` KAMEZAWA Hiroyuki
2008-08-20  9:53 ` [RFC][PATCH -mm 0/7] memcg: lockless page_cgroup v1 KAMEZAWA Hiroyuki
2008-08-20  9:55   ` [RFC][PATCH -mm 1/7] memcg: page_cgroup_atomic_flags.patch KAMEZAWA Hiroyuki
2008-08-20  9:59   ` [RFC][PATCH -mm 2/7] memcg: delayed_batch_freeing_of_page_cgroup.patch KAMEZAWA Hiroyuki
2008-08-20 10:03   ` [RFC][PATCH -mm 3/7] memcg: freeing page_cgroup by rcu.patch KAMEZAWA Hiroyuki
2008-08-20 10:04   ` [RFC][PATCH -mm 4/7] memcg: lockless page_cgroup KAMEZAWA Hiroyuki
2008-08-20 10:05   ` [RFC][PATCH -mm 5/7] memcg: prefetch mem cgroup per zone KAMEZAWA Hiroyuki
2008-08-20 10:07   ` [RFC][PATCH -mm 6/7] memcg: make-mapping-null-before-calling-uncharge.patch KAMEZAWA Hiroyuki
2008-08-22  4:57     ` Daisuke Nishimura
2008-08-22  5:48       ` KAMEZAWA Hiroyuki
2008-08-20 10:08   ` [RFC][PATCH -mm 7/7] memcg: add page_cgroup.h header file KAMEZAWA Hiroyuki
2008-08-20 10:41   ` [RFC][PATCH -mm 0/7] memcg: lockless page_cgroup v1 KAMEZAWA Hiroyuki
2008-08-20 11:00     ` KAMEZAWA Hiroyuki
2008-08-21  2:17       ` KAMEZAWA Hiroyuki
2008-08-21  3:36         ` Balbir Singh
2008-08-21  3:58           ` KAMEZAWA Hiroyuki
2008-08-21  3:54         ` Daisuke Nishimura
2008-08-21  8:34       ` KAMEZAWA Hiroyuki
2008-08-20 11:33   ` Hirokazu Takahashi

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=20080819181150.3a84f5dd.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryov@valinux.co.jp \
    --cc=yamamoto@valinux.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

all inboxes | Powered by JetHome®