From: Andi Kleen <andi@firstfloor.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
fujita.tomonori@lab.ntt.co.jp
Subject: Re: [RFC][PATCH 1/3] contigous big page allocator
Date: Wed, 13 Oct 2010 10:36:53 +0200 [thread overview]
Message-ID: <87ocay1obe.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20101013161206.c29df8ea.kamezawa.hiroyu@jp.fujitsu.com> (KAMEZAWA Hiroyuki's message of "Wed, 13 Oct 2010 16:12:06 +0900")
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
>> > My intention is not for allocating HUGEPAGE(> MAX_ORDER).
>>
>> I still believe using this for 1GB pages would be one of the more
>> interesting use cases.
>>
>
> I'm successfully allocating 1GB of continous pages at test. But I'm not sure
> requirements and users. How quick this allocation should be ?
This will always be slow. Huge pages are always pre allocated
even today through a sysctl. The use case would be have
echo XXX > /proc/sys/vm/nr_hugepages
at runtime working for 1GB too, instead of requiring a reboot
for this.
I think it's ok if that is somewhat slow, as long as it is not
incredible slow. Ideally it shouldn't cause a swap storm either
(maybe we need some way to indicate how hard the freeing code should
try?)
I guess it would only really work well if you predefine
movable zones at boot time.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
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:[~2010-10-13 8:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 3:15 KAMEZAWA Hiroyuki
2010-10-13 3:17 ` [RFC][PATCH 2/3] find a contiguous range KAMEZAWA Hiroyuki
2010-10-17 3:18 ` Minchan Kim
2010-10-18 0:29 ` KAMEZAWA Hiroyuki
2010-10-13 3:18 ` [RFC][PATCH 3/3] alloc contig pages with migration KAMEZAWA Hiroyuki
2010-10-17 4:05 ` Minchan Kim
2010-10-18 0:35 ` KAMEZAWA Hiroyuki
2010-10-18 5:18 ` Minchan Kim
2010-10-18 5:31 ` KAMEZAWA Hiroyuki
2010-10-18 5:52 ` Minchan Kim
2010-10-18 5:52 ` KAMEZAWA Hiroyuki
2010-10-13 5:05 ` [RFC][PATCH 1/3] contigous big page allocator KOSAKI Motohiro
2010-10-13 7:01 ` Andi Kleen
2010-10-13 7:12 ` KAMEZAWA Hiroyuki
2010-10-13 8:36 ` Andi Kleen [this message]
2010-10-13 8:39 ` KAMEZAWA Hiroyuki
2010-10-14 1:59 ` KOSAKI Motohiro
2010-10-14 7:07 ` FUJITA Tomonori
2010-10-14 7:24 ` Andi Kleen
2010-10-14 8:36 ` FUJITA Tomonori
2010-10-14 12:55 ` Andi Kleen
2010-10-14 15:09 ` FUJITA Tomonori
2010-10-14 12:10 ` Felipe Contreras
2010-10-14 12:09 ` Felipe Contreras
2010-10-14 15:24 ` FUJITA Tomonori
2010-10-14 21:50 ` Felipe Contreras
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=87ocay1obe.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.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