linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Michal Hocko <mhocko@suse.cz>, Hugh Dickins <hughd@google.com>,
	Han Ying <yinghan@google.com>,
	Glauber Costa <glommer@parallels.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"suleiman@google.com" <suleiman@google.com>,
	"n-horiguchi@ah.jp.nec.com" <n-horiguchi@ah.jp.nec.com>,
	Tejun Heo <tj@kernel.org>
Subject: Re: [RFC][PATCH 0/3] page cgroup diet
Date: Wed, 21 Mar 2012 15:30:22 +0900	[thread overview]
Message-ID: <4F69757E.5030103@jp.fujitsu.com> (raw)
In-Reply-To: <4F69718E.8010603@openvz.org>

(2012/03/21 15:13), Konstantin Khlebnikov wrote:

> KAMEZAWA Hiroyuki wrote:
>> (2012/03/20 4:59), Konstantin Khlebnikov wrote:
>>
>>> KAMEZAWA Hiroyuki wrote:
>>>> This is just an RFC...test is not enough yet.
>>>>
>>>> I know it's merge window..this post is just for sharing idea.
>>>>
>>>> This patch merges pc->flags and pc->mem_cgroup into a word. Then,
>>>> memcg's overhead will be 8bytes per page(4096bytes?).
>>>>
>>>> Because this patch will affect all memory cgroup developers, I'd like to
>>>> show patches before MM Summit. I think we can agree the direction to
>>>> reduce size of page_cgroup..and finally integrate into 'struct page'
>>>> (and remove cgroup_disable= boot option...)
>>>>
>>>> Patch 1/3 - introduce pc_to_mem_cgroup and hide pc->mem_cgroup
>>>> Patch 2/3 - remove pc->mem_cgroup
>>>> Patch 3/3 - remove memory barriers.
>>>>
>>>> I'm now wondering when this change should be merged....
>>>>
>>>
>>> This is cool, but maybe we should skip this temporary step and merge all this stuff into page->flags.
>>
>>
>> Why we should skip and delay reduction of size of page_cgroup
>> which is considered as very big problem ?
> 
> I think it would be better to solve problem completely and kill page_cgroup in one step.
> 


I like step-by-step rather than a big step. I devided this page_cgroup diet patch set
into 3 steps (2012-Jan, 2012-Feb, and the next one is the last.)

This change may introduce new races as step1 and step2 did (Thanks to Hugh Dickins!).

Finally, IIUC, 'struct page' has 8bytes of padding now. I think we can use that space
if we can be agreed.

Hm. BTW, using lruvec in page->flags implies you add a dynamic table lookup in
free_page() and you need to reset page->flags to point a valid
lruvec at page allocation. Please take care of performance.

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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2012-03-21  6:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  7:56 KAMEZAWA Hiroyuki
2012-03-19  7:59 ` [RFC][PATCH 1/3] memcg: add methods to access pc->mem_cgroup KAMEZAWA Hiroyuki
2012-03-19 10:58   ` Glauber Costa
2012-03-19 12:11     ` KAMEZAWA Hiroyuki
2012-03-19 12:29       ` Glauber Costa
2012-03-19 15:33     ` Michal Hocko
2012-03-19 15:34       ` Glauber Costa
2012-03-21  1:06       ` KAMEZAWA Hiroyuki
2012-03-22 13:11   ` Michal Hocko
2012-03-19  8:01 ` [RFC][PATCH 2/3] memcg: reduce size of struct page_cgroup KAMEZAWA Hiroyuki
2012-03-19 22:20   ` Suleiman Souhlal
2012-03-21  0:47     ` KAMEZAWA Hiroyuki
2012-03-22 13:11   ` Michal Hocko
2012-03-19  8:03 ` [RFC][PATCH 3/3] memcg: atomic update of memcg pointer and other bits KAMEZAWA Hiroyuki
2012-03-22 13:38   ` Michal Hocko
2012-03-23  1:03     ` KAMEZAWA Hiroyuki
2012-03-23  8:54       ` Michal Hocko
2012-03-19 19:59 ` [RFC][PATCH 0/3] page cgroup diet Konstantin Khlebnikov
2012-03-21  1:02   ` KAMEZAWA Hiroyuki
2012-03-21  6:13     ` Konstantin Khlebnikov
2012-03-21  6:30       ` 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=4F69757E.5030103@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cgroups@vger.kernel.org \
    --cc=glommer@parallels.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=khlebnikov@openvz.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=suleiman@google.com \
    --cc=tj@kernel.org \
    --cc=yinghan@google.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