From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
xemul@openvz.org, "hugh@veritas.com" <hugh@veritas.com>
Subject: Re: [PATCH 5/7] radix-tree page cgroup
Date: Wed, 19 Mar 2008 11:51:03 +0900 [thread overview]
Message-ID: <20080319115103.c361969d.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080319020536.GE24473@balbir.in.ibm.com>
On Wed, 19 Mar 2008 07:35:36 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > +#include <linux/mm.h>
> > +#include <linux/slab.h>
> > +#include <linux/radix-tree.h>
> > +#include <linux/memcontrol.h>
> > +#include <linux/page_cgroup.h>
> > +#include <linux/err.h>
> > +
> > +
> > +
>
> Too many extra lines
>
fixed.
> > +#define PCGRP_SHIFT (CONFIG_CGROUP_PAGE_CGROUP_ORDER)
> > +#define PCGRP_SIZE (1 << PCGRP_SHIFT)
> > +
> > +struct page_cgroup_head {
> > + struct page_cgroup pc[PCGRP_SIZE];
>
> Are we over optimizing here?
>
what is over optimizing ? PCGRP_SIZE is too large ?
> > +};
> > +
> > +struct page_cgroup_root {
> > + spinlock_t tree_lock;
> > + struct radix_tree_root root_node;
> > +};
> > +
>
> Comments describing induvidual members of the structures would be nice
>
will add.
> > +static struct page_cgroup_root *root_dir[MAX_NUMNODES];
> > +
>
>
> The root_dir is per node, should we call it node_root_dir?
>
ok.
>
> > + root = root_dir[nid];
> > + /* Before Init ? */
> > + if (unlikely(!root))
> > + return NULL;
> > +
>
> Shouldn't this be a BUG_ON? We don't expect any user space pages to be
> allocated prior to init.
No. this routine uses kmalloc(). To use it, I uses late_initcall().
Before late_initcall(), pages will be used.
>
> > + base_pfn = idx << PCGRP_SHIFT;
> > +retry:
> > + error = 0;
> > + rcu_read_lock();
> > + head = radix_tree_lookup(&root->root_node, idx);
> > + rcu_read_unlock();
> > +
> > + if (likely(head))
> > + return &head->pc[pfn - base_pfn];
> > + if (allocate == false)
> > + return NULL;
> > +
> > + /* Very Slow Path. On demand allocation. */
> > + gfpmask = gfpmask & ~(__GFP_HIGHMEM | __GFP_MOVABLE);
> > +
> > + head = alloc_init_page_cgroup(base_pfn, nid, gfpmask);
>
> This name is a bit confusing, it sounds like the page_cgroup is
> allocated from initialzation context, but I think it stands for
> allocate and initialize right?
>
Ah, yes. I'll rename this.
> > + if (!head)
> > + return ERR_PTR(-ENOMEM);
> > + pc = NULL;
> > + error = radix_tree_preload(gfpmask);
> > + if (error)
> > + goto out;
> > + spin_lock_irqsave(&root->tree_lock, flags);
> > + error = radix_tree_insert(&root->root_node, idx, head);
> > +
> > + if (!error)
> > + pc = &head->pc[pfn - base_pfn];
> > + spin_unlock_irqrestore(&root->tree_lock, flags);
> > + radix_tree_preload_end();
> > +out:
> > + if (!pc) {
> > + free_page_cgroup(head);
>
> We free the entire page_cgroup_head?
>
yes. We alloc a head and free a head.
> > + if (error == -EEXIST)
> > + goto retry;
> > + }
> > + if (error)
> > + pc = ERR_PTR(error);
> > + return pc;
> > +}
> > +
> > +__init int page_cgroup_init(void)
> > +{
> > + int nid;
> > + struct page_cgroup_root *root;
> > +
> > + page_cgroup_cachep = kmem_cache_create("page_cgroup",
> > + sizeof(struct page_cgroup_head), 0,
> > + SLAB_PANIC | SLAB_DESTROY_BY_RCU, NULL);
> > + if (!page_cgroup_cachep) {
> > + printk(KERN_ERR "page accouning setup failure\n");
> > + printk(KERN_ERR "can't initialize slab memory\n");
> > + /* FIX ME: should return some error code ? */
> > + return 0;
> > + }
> > + for_each_online_node(nid) {
> > + if (node_state(nid, N_NORMAL_MEMORY)
> > + root = kmalloc_node(sizeof(struct page_cgroup_root),
> > + GFP_KERNEL, nid);
> > + else
> > + root = kmalloc(sizeof(struct page_cgroup_root),
> > + GFP_KERNEL);
> > + INIT_RADIX_TREE(&root->root_node, GFP_ATOMIC);
> > + spin_lock_init(&root->tree_lock);
> > + smp_wmb();
>
> Could you please explain why we need a barrier here and comment it as
> well.
ok. will add.
Before root_dir[nid] != NULL is visible to other cpus, all initizlization to
root should be finished.
> > + root_dir[nid] = root;
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>
next prev parent reply other threads:[~2008-03-19 2:51 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 9:59 [PATCH 0/7] memcg: radix-tree page_cgroup KAMEZAWA Hiroyuki
2008-03-14 10:03 ` [PATCH 1/7] re-define page_cgroup KAMEZAWA Hiroyuki
2008-03-16 14:15 ` Balbir Singh
2008-03-18 1:10 ` KAMEZAWA Hiroyuki
2008-03-17 0:21 ` Li Zefan
2008-03-18 1:12 ` KAMEZAWA Hiroyuki
2008-03-17 2:07 ` Li Zefan
2008-03-18 1:11 ` KAMEZAWA Hiroyuki
2008-03-14 10:06 ` [PATCH 2/7] charge/uncharge KAMEZAWA Hiroyuki
2008-03-17 1:46 ` Balbir Singh
2008-03-18 1:14 ` KAMEZAWA Hiroyuki
2008-03-17 2:26 ` Li Zefan
2008-03-18 1:15 ` KAMEZAWA Hiroyuki
2008-03-14 10:07 ` [PATCH 3/7] memcg: move_lists KAMEZAWA Hiroyuki
2008-03-18 16:44 ` Balbir Singh
2008-03-19 2:34 ` KAMEZAWA Hiroyuki
2008-03-14 10:15 ` [PATCH 4/7] memcg: page migration KAMEZAWA Hiroyuki
2008-03-17 2:36 ` Li Zefan
2008-03-18 1:17 ` KAMEZAWA Hiroyuki
2008-03-18 18:11 ` Balbir Singh
2008-03-19 2:44 ` KAMEZAWA Hiroyuki
2008-03-14 10:17 ` [PATCH 5/7] radix-tree page cgroup KAMEZAWA Hiroyuki
2008-03-17 2:56 ` Li Zefan
2008-03-17 3:26 ` Li Zefan
2008-03-18 1:18 ` KAMEZAWA Hiroyuki
2008-03-18 1:23 ` KAMEZAWA Hiroyuki
2008-03-19 2:05 ` Balbir Singh
2008-03-19 2:51 ` KAMEZAWA Hiroyuki [this message]
2008-03-19 3:14 ` Balbir Singh
2008-03-19 3:24 ` KAMEZAWA Hiroyuki
2008-03-19 21:11 ` Peter Zijlstra
2008-03-20 4:45 ` KAMEZAWA Hiroyuki
2008-03-20 5:09 ` KAMEZAWA Hiroyuki
2008-03-14 10:18 ` [PATCH 6/7] memcg: speed up by percpu KAMEZAWA Hiroyuki
2008-03-17 3:03 ` Li Zefan
2008-03-18 1:25 ` KAMEZAWA Hiroyuki
2008-03-18 23:55 ` Li Zefan
2008-03-19 2:51 ` KAMEZAWA Hiroyuki
2008-03-19 21:19 ` Peter Zijlstra
2008-03-19 21:41 ` Peter Zijlstra
2008-03-20 9:08 ` Andy Whitcroft
2008-03-20 4:46 ` KAMEZAWA Hiroyuki
2008-03-14 10:22 ` [PATCH 7/7] memcg: freeing page_cgroup at suitable chance KAMEZAWA Hiroyuki
2008-03-17 3:10 ` Li Zefan
2008-03-18 1:30 ` KAMEZAWA Hiroyuki
2008-03-19 21:33 ` Peter Zijlstra
2008-03-20 5:07 ` KAMEZAWA Hiroyuki
2008-03-20 7:55 ` Peter Zijlstra
2008-03-20 14:49 ` kamezawa.hiroyu
2008-03-20 16:04 ` kamezawa.hiroyu
2008-03-20 16:09 ` Peter Zijlstra
2008-03-20 16:15 ` kamezawa.hiroyu
2008-03-15 6:15 ` [PATCH 0/7] memcg: radix-tree page_cgroup 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=20080319115103.c361969d.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=xemul@openvz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox