linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.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 2/5] use ID in page cgroup
Date: Tue, 3 Aug 2010 12:48:31 +0900	[thread overview]
Message-ID: <20100803124831.8cd5976f.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20100803034513.GF3863@balbir.in.ibm.com>

On Tue, 3 Aug 2010 09:15:13 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2010-08-02 19:14:10]:
> 
> > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > 
> > Now, addresses of memory cgroup can be calculated by their ID without complex.
> > This patch relplaces pc->mem_cgroup from a pointer to a unsigned short.
> > On 64bit architecture, this offers us more 6bytes room per page_cgroup.
> > Use 2bytes for blkio-cgroup's page tracking. More 4bytes will be used for
> > some light-weight concurrent access.
> > 
> > We may able to move this id onto flags field but ...go step by step.
> > 
> > Changelog: 20100730
> >  - fixed some garbage added by debug code in early stage
> > 
> > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > ---
> >  include/linux/page_cgroup.h |    3 ++-
> >  mm/memcontrol.c             |   32 +++++++++++++++++++-------------
> >  mm/page_cgroup.c            |    2 +-
> >  3 files changed, 22 insertions(+), 15 deletions(-)
> > 
> > Index: mmotm-0727/include/linux/page_cgroup.h
> > ===================================================================
> > --- mmotm-0727.orig/include/linux/page_cgroup.h
> > +++ mmotm-0727/include/linux/page_cgroup.h
> > @@ -12,7 +12,8 @@
> >   */
> >  struct page_cgroup {
> >  	unsigned long flags;
> > -	struct mem_cgroup *mem_cgroup;
> > +	unsigned short mem_cgroup;	/* ID of assigned memory cgroup */
> > +	unsigned short blk_cgroup;	/* Not Used..but will be. */
> >  	struct page *page;
> >  	struct list_head lru;		/* per cgroup LRU list */
> >  };
> 
> Can I recommend that on 64 bit systems, we merge the flag, mem_cgroup
> and blk_cgroup into one 8 byte value. We could use
> __attribute("packed") and do something like this
> 

It's a next step.

> struct page_cgroup {
>         unsigned int flags;
>         unsigned short mem_cgroup;
>         unsigned short blk_cgroup;
>         ...
> } __attribute(("packed"));
> 
> Then we need to make sure we don't use more that 32 bits for flags,
> which is very much under control at the moment.
> 
set_bit() requires "long" as its argument. more some trick is required.

 And, IIUC, packing implies
	pc->mem_cgroup = mem_cgroup_id; or
	pc->blk_cgroup = blk_cgroup_id; will have race with
	set/clear_bit(BIT_XXXX, &pc->flags)
 
 This "packing" is not very easy. we have to consider all possible combinations
 of operations.

> This will save us 8 bytes in total on 64 bit systems and nothing on 32
> bit systems, but will enable blkio cgroup to co-exist.
> 

yes. But I have cocnerns of race condition. to do that, we need
patch 3-5. (But patch 5 adds spinlock, then no 8bytes reduce.)

Let me go step by step. I'm _really_ afraid of race conditions.

Thanks,
-Kame

--
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>

  reply	other threads:[~2010-08-03  3:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 10:11 [PATCH -mm 0/5] towards I/O aware memory cgroup v3 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 [this message]
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 ` [PATCH -mm 0/5] towards I/O aware memory cgroup v3 Balbir Singh

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=20100803124831.8cd5976f.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=gthelen@google.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