From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"xemul@openvz.org" <xemul@openvz.org>,
"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com
Subject: Re: [RFC][PATCH 0/3] memcg: remove refcnt
Date: Fri, 11 Apr 2008 10:27:37 +0530 [thread overview]
Message-ID: <47FEEFC1.4080509@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080408190734.70ab55b0.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> This patch is based on 2.6.25-rc8-mm1 + mem_cgroup_per_zone() fix.
> (already in -mm)
>
> This patch is a set for removing refcnt from memory resource controller's
> page_cgroup. Instead of ref_cnt, this patch uses page_mapped().
> By this, we can avoid unnecesary locks and calls to some extent.
>
> Brief Patch Desc.
> [1/3] change migration handling .... charge new-page before migration.
> [2/3] remove refcnt .... remove refcnt from page_cgroup.
> [3/3] handle swapcache .... handle swapcache again.
>
> [1/3] works for better page migration handling.
> [2/3] works for better speed. (depends on [1/3])
> [3/3] works for swap-cache. (depends on [2/3])
>
>
>
> Unix bench execl result(ia64):
> No controller : 43.0 2654.7 617.4
> with controller : 43.0 2461.3 572.4
> after this patch: 43.0 2553.6 593.9
>
> If page_cgroup->ref_cnt is necessary (for some purpose), please tell me.
>
> Plan:
> I'd like to push this set before complicated radix-tree page_cgroup set.
> But this should be reviewd before going ahead.
>
I think this makes a lot of sense. We can push the optimizations independent of
the radix tree, so that it is easy to debug and develop.
--
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>
next parent reply other threads:[~2008-04-11 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080408190734.70ab55b0.kamezawa.hiroyu@jp.fujitsu.com>
2008-04-11 4:57 ` Balbir Singh [this message]
[not found] ` <20080408191311.73b167bb.kamezawa.hiroyu@jp.fujitsu.com>
2008-04-11 12:20 ` [RFC][PATCH 3/3] account swapcache Daisuke Nishimura
2008-04-14 0:47 ` KAMEZAWA Hiroyuki
2008-04-14 8:03 ` Daisuke Nishimura
2008-04-14 8:23 ` KAMEZAWA Hiroyuki
2008-04-14 8:36 ` Daisuke Nishimura
2008-04-14 8:45 ` 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=47FEEFC1.4080509@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=xemul@openvz.org \
--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 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.