From: Michal Hocko <mhocko@suse.cz>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] page_cgroup: Reduce allocation overhead for page_cgroup array for CONFIG_SPARSEMEM v2
Date: Thu, 24 Feb 2011 14:40:45 +0100 [thread overview]
Message-ID: <20110224134045.GA22122@tiehlicka.suse.cz> (raw)
In-Reply-To: <1298485162.7236.4.camel@nimitz>
Here is the second version of the patch. I have used alloc_pages_exact
instead of the complex double array approach.
I still fallback to kmalloc/vmalloc because hotplug can happen quite
some time after boot and we can end up not having enough continuous
pages at that time.
I am also thinking whether it would make sense to introduce
alloc_pages_exact_node function which would allocate pages from the
given node.
Any thoughts?
---
next prev parent reply other threads:[~2011-02-24 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 15:10 [RFC PATCH] page_cgroup: Reduce allocation overhead for page_cgroup array for CONFIG_SPARSEMEM Michal Hocko
2011-02-23 18:19 ` Dave Hansen
2011-02-23 23:52 ` KAMEZAWA Hiroyuki
2011-02-24 9:35 ` Michal Hocko
2011-02-24 10:02 ` KAMEZAWA Hiroyuki
2011-02-24 9:33 ` Michal Hocko
2011-02-24 13:40 ` Michal Hocko [this message]
2011-02-25 3:25 ` [RFC PATCH] page_cgroup: Reduce allocation overhead for page_cgroup array for CONFIG_SPARSEMEM v2 KAMEZAWA Hiroyuki
2011-02-25 9:53 ` [RFC PATCH] page_cgroup: Reduce allocation overhead for page_cgroup array for CONFIG_SPARSEMEM v3 Michal Hocko
2011-02-28 0:53 ` KAMEZAWA Hiroyuki
2011-02-28 9:12 ` [RFC PATCH] page_cgroup: Reduce allocation overhead for page_cgroup array for CONFIG_SPARSEMEM v4 Michal Hocko
2011-02-28 9:23 ` KAMEZAWA Hiroyuki
2011-02-28 9:53 ` Michal Hocko
2011-02-28 9:48 ` KAMEZAWA Hiroyuki
2011-02-28 10:12 ` Michal Hocko
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=20110224134045.GA22122@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=dave@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).