From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
"Luck, Tony" <tony.luck@intel.com>, Andi Kleen <ak@suse.de>,
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
x86-64 Discuss <discuss@x86-64.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes
Date: Wed, 15 Feb 2006 01:06:39 +0000 [thread overview]
Message-ID: <43F27E9F.9030005@jp.fujitsu.com> (raw)
In-Reply-To: <20060214221413.ECF3.Y-GOTO@jp.fujitsu.com>
Yasunori Goto wrote:
> + if (system_state = SYSTEM_RUNNING){
> + unsigned long queue_head_size = 1;
> + while (queue_head_size < sizeof(wait_queue_head_t))
> + queue_head_size <<= 1;
> +
> + pages = (1 << (PAGE_SHIFT + 3)) / queue_head_size;
> + }
> +
we have to kmalloc() wait_table after this.
I don't think we always succeed to alloc multiple contiguous pages by kmalloc().
How about allocating wait_table like this ?
=
size = 4096; /* 4096 is maximum size */
while(size) {
waittable = kmalloc(size * sizeof(wait_queue_head_t), GFP_KERNEL):
if (wait_table)
break;
size = size >> 1;
}
zone->wait_table_size = size;
zone->wait_table_bits = wait_table_bits(zone->wait_table_size);
zone->wait_table = wait_table;
=
-- Kame
WARNING: multiple messages have this Message-ID (diff)
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Dave Hansen <haveblue@us.ibm.com>,
"Luck, Tony" <tony.luck@intel.com>, Andi Kleen <ak@suse.de>,
"Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
x86-64 Discuss <discuss@x86-64.org>,
Linux Hotplug Memory Support <lhms-devel@lists.sourceforge.net>
Subject: Re: [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization)
Date: Wed, 15 Feb 2006 10:06:39 +0900 [thread overview]
Message-ID: <43F27E9F.9030005@jp.fujitsu.com> (raw)
In-Reply-To: <20060214221413.ECF3.Y-GOTO@jp.fujitsu.com>
Yasunori Goto wrote:
> + if (system_state == SYSTEM_RUNNING){
> + unsigned long queue_head_size = 1;
> + while (queue_head_size < sizeof(wait_queue_head_t))
> + queue_head_size <<= 1;
> +
> + pages = (1 << (PAGE_SHIFT + 3)) / queue_head_size;
> + }
> +
we have to kmalloc() wait_table after this.
I don't think we always succeed to alloc multiple contiguous pages by kmalloc().
How about allocating wait_table like this ?
==
size = 4096; /* 4096 is maximum size */
while(size) {
waittable = kmalloc(size * sizeof(wait_queue_head_t), GFP_KERNEL):
if (wait_table)
break;
size = size >> 1;
}
zone->wait_table_size = size;
zone->wait_table_bits = wait_table_bits(zone->wait_table_size);
zone->wait_table = wait_table;
==
-- Kame
next prev parent reply other threads:[~2006-02-15 1:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 14:20 [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists i Yasunori Goto
2006-02-10 14:20 ` [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Yasunori Goto
2006-02-10 16:32 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes Dave Hansen
2006-02-10 16:32 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Dave Hansen
2006-02-11 4:15 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait tabl Yasunori Goto
2006-02-11 4:15 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Yasunori Goto
2006-02-11 10:58 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes Kamezawa Hiroyuki
2006-02-11 10:58 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Kamezawa Hiroyuki
2006-02-14 13:24 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait tabl Yasunori Goto
2006-02-14 13:24 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Yasunori Goto
2006-02-15 1:06 ` KAMEZAWA Hiroyuki [this message]
2006-02-15 1:06 ` KAMEZAWA Hiroyuki
2006-02-10 16:33 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes Dave Hansen
2006-02-10 16:33 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Dave Hansen
2006-02-14 7:34 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait tabl Yasunori Goto
2006-02-14 7:34 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Yasunori Goto
2006-02-10 21:59 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes Joel Schopp
2006-02-10 21:59 ` [Lhms-devel] [RFC/PATCH: 002/010] Memory hotplug for new nodes with pgdat allocation. (Wait table and zonelists initalization) Joel Schopp
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=43F27E9F.9030005@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=haveblue@us.ibm.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=tony.luck@intel.com \
--cc=y-goto@jp.fujitsu.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 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.