All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: KAMEZAWA Hiroyuki
	<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Cc: "containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org"
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	"linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org"
	<linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
	"yamamoto-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org"
	<yamamoto-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
Subject: Re: [RFC][PATCH] memory controller per zone patches take 2 [9/10] per-zone-lru for memory cgroup
Date: Mon, 19 Nov 2007 11:51:15 +0530	[thread overview]
Message-ID: <47412B5B.80409@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071119104826.e4ba02ca.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>

KAMEZAWA Hiroyuki wrote:
> On Sat, 17 Nov 2007 23:21:22 +0530
> Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> wrote:
> 
>> Thanks, this has been a long pending TODO. What is pending now on my
>> plate is re-organizing res_counter to become aware of the filesystem
>> hierarchy. I want to split out the LRU lists from the memory controller
>> and resource counters.
>>
> Does "file system hierarchy" here means "control group hierarchy" ?
> like

Yes, you are right

> =
> /cgroup/group_A/group_A_1
>             .  /group_A_2
>                /group_A_3
> (LRU(s) will be used for maintaining parent/child groups.)
> 

The LRU's will be shared, my vision is

		LRU
		^ ^
		| |
	Mem-----+ +----Mem


That two or more mem_cgroup's can refer to the same LRU list and have
their own resource counters. This setup will be used in the case
of a hierarchy, so that a child can share memory with its parent
and have it's own limit.

The mem_cgroup will basically then only contain a reference
to the LRU list.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

WARNING: multiple messages have this Message-ID (diff)
From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "containers@lists.osdl.org" <containers@lists.osdl.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>
Subject: Re: [RFC][PATCH] memory controller per zone patches take 2 [9/10] per-zone-lru for memory cgroup
Date: Mon, 19 Nov 2007 11:51:15 +0530	[thread overview]
Message-ID: <47412B5B.80409@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071119104826.e4ba02ca.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> On Sat, 17 Nov 2007 23:21:22 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> 
>> Thanks, this has been a long pending TODO. What is pending now on my
>> plate is re-organizing res_counter to become aware of the filesystem
>> hierarchy. I want to split out the LRU lists from the memory controller
>> and resource counters.
>>
> Does "file system hierarchy" here means "control group hierarchy" ?
> like

Yes, you are right

> =
> /cgroup/group_A/group_A_1
>             .  /group_A_2
>                /group_A_3
> (LRU(s) will be used for maintaining parent/child groups.)
> 

The LRU's will be shared, my vision is

		LRU
		^ ^
		| |
	Mem-----+ +----Mem


That two or more mem_cgroup's can refer to the same LRU list and have
their own resource counters. This setup will be used in the case
of a hierarchy, so that a child can share memory with its parent
and have it's own limit.

The mem_cgroup will basically then only contain a reference
to the LRU list.

-- 
	Warm Regards,
	Balbir Singh
	Linux Technology Center
	IBM, ISTL

--
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:[~2007-11-19  6:21 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 10:11 [RFC][PATCH] memory controller per zone patches take 2 [0/10] introduction KAMEZAWA Hiroyuki
2007-11-16 10:11 ` KAMEZAWA Hiroyuki
     [not found] ` <20071116191107.46dd523a.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-16 10:14   ` [RFC][PATCH] memory controller per zone patches take 2 [1/10] add scan_global_lru() macro KAMEZAWA Hiroyuki
2007-11-16 10:14     ` KAMEZAWA Hiroyuki
     [not found]     ` <20071116191459.dcd71a3d.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-17  9:03       ` Balbir Singh
2007-11-17  9:03         ` Balbir Singh
2007-11-16 10:16   ` [RFC][PATCH] memory controller per zone patches take 2 [2/10] add nid/zid function for page_cgroup KAMEZAWA Hiroyuki
2007-11-16 10:16     ` KAMEZAWA Hiroyuki
     [not found]     ` <20071116191635.2c141c38.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-17  9:15       ` Balbir Singh
2007-11-17  9:15         ` Balbir Singh
     [not found]         ` <473EB141.4000005-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-19  1:37           ` KAMEZAWA Hiroyuki
2007-11-19  1:37             ` KAMEZAWA Hiroyuki
2007-11-16 10:17   ` [RFC][PATCH] memory controller per zone patches take 2 [3/10] add per zone active/inactive counter to mem_cgroup KAMEZAWA Hiroyuki
2007-11-16 10:17     ` KAMEZAWA Hiroyuki
     [not found]     ` <20071116191744.d8e2b3a5.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-17 16:07       ` Balbir Singh
2007-11-17 16:07         ` Balbir Singh
2007-11-16 10:18   ` [RFC][PATCH] memory controller per zone patches take 2 [4/10] calculate mapped ratio for memory cgroup KAMEZAWA Hiroyuki
2007-11-16 10:18     ` KAMEZAWA Hiroyuki
     [not found]     ` <20071116191844.319b2754.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-17 16:12       ` Balbir Singh
2007-11-17 16:12         ` Balbir Singh
     [not found]         ` <473F12D6.8030607-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-19  1:42           ` KAMEZAWA Hiroyuki
2007-11-19  1:42             ` KAMEZAWA Hiroyuki
     [not found]             ` <20071119104246.d38de797.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-22  8:34               ` YAMAMOTO Takashi
2007-11-22  8:34                 ` YAMAMOTO Takashi
     [not found]                 ` <20071122083421.49E681CEE8C-Pcsii4f/SVk@public.gmane.org>
2007-11-22  8:40                   ` KAMEZAWA Hiroyuki
2007-11-22  8:40                     ` KAMEZAWA Hiroyuki
     [not found]                     ` <20071122174015.c5ef61ae.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-22  8:46                       ` YAMAMOTO Takashi
2007-11-22  8:46                         ` YAMAMOTO Takashi
     [not found]                     ` <20071122084647.485981CEE98-Pcsii4f/SVk@public.gmane.org>
2007-11-22 13:31                       ` kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A
2007-11-22 13:31                         ` kamezawa.hiroyu
2007-11-16 10:22   ` [RFC][PATCH] memory controller per zone patches take 2 [5/10] calculate active/inactive balance " KAMEZAWA Hiroyuki
2007-11-16 10:22     ` KAMEZAWA Hiroyuki
2007-11-16 10:23   ` [RFC][PATCH] memory controller per zone patches take 2 [6/10] remember reclaim priority " KAMEZAWA Hiroyuki
2007-11-16 10:23     ` KAMEZAWA Hiroyuki
2007-11-16 10:24   ` [RFC][PATCH] memory controller per zone patches take 2 [7/10] calculate reclaim scan number " KAMEZAWA Hiroyuki
2007-11-16 10:24     ` KAMEZAWA Hiroyuki
2007-11-16 10:25   ` [RFC][PATCH] memory controller per zone patches take 2 [8/10] changes in vmscan.c KAMEZAWA Hiroyuki
2007-11-16 10:25     ` KAMEZAWA Hiroyuki
     [not found]     ` <20071116192536.0a9f2d61.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-17 17:37       ` Balbir Singh
2007-11-17 17:37         ` Balbir Singh
2007-11-16 10:26   ` [RFC][PATCH] memory controller per zone patches take 2 [9/10] per-zone-lru for memory cgroup KAMEZAWA Hiroyuki
2007-11-16 10:26     ` KAMEZAWA Hiroyuki
     [not found]     ` <20071116192642.8c7f07c9.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-17 17:51       ` Balbir Singh
2007-11-17 17:51         ` Balbir Singh
     [not found]         ` <473F2A1A.8000703-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-19  1:48           ` KAMEZAWA Hiroyuki
2007-11-19  1:48             ` KAMEZAWA Hiroyuki
     [not found]             ` <20071119104826.e4ba02ca.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-19  6:21               ` Balbir Singh [this message]
2007-11-19  6:21                 ` Balbir Singh
     [not found]                 ` <47412B5B.80409-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2007-11-19  6:35                   ` KAMEZAWA Hiroyuki
2007-11-19  6:35                     ` KAMEZAWA Hiroyuki
     [not found]                     ` <20071119153549.d6f6f1de.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-11-19  8:34                       ` Balbir Singh
2007-11-19  8:34                         ` Balbir Singh
2007-11-16 10:27   ` [RFC][PATCH] memory controller per zone patches take 2 [10/10] per-zone-lock " KAMEZAWA Hiroyuki
2007-11-16 10:27     ` KAMEZAWA Hiroyuki

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=47412B5B.80409@linux.vnet.ibm.com \
    --to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=yamamoto-jCdQPDEk3idL9jVzuh4AOg@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.