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>,
Mel Gorman <mel@csn.ul.ie>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [RFC][PATCH] big continuous memory allocator v2
Date: Tue, 7 Sep 2010 11:45:38 +0200 [thread overview]
Message-ID: <20100907114538.71fc2dcd@basil.nowhere.org> (raw)
In-Reply-To: <20100907180354.a8dd5669.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 7 Sep 2010 18:03:54 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Oh, I didn't consider that. Hmm. If x86 really wants to support 1GB
> page, MAX_ORDER should be raised. (I'm sorry if it was already
> disccused.)
That doesn't really work, it requires alignment of all the
zones to 1GB too (not practical) and has a lot of overhead.
Also for the normal case it wouldn't work anyways due to fragmentation.
> > One issue is also that it would be good to be able to decide
> > in advance if the OOM killer is likely triggered (and if yes
> > reject the allocation in the first place).
> >
>
> Checking the amount of memory and swap before starts ?
> It sounds nice. I'd like to add something.
That would be the simple variant, but perhaps it could
even consider parallel traffic? (I guess that would
be difficult) Or perhaps bail out early if OOM is likely.
-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-09-07 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 2:45 KAMEZAWA Hiroyuki
2010-09-07 7:29 ` Andi Kleen
2010-09-07 8:25 ` KAMEZAWA Hiroyuki
2010-09-07 8:46 ` Andi Kleen
2010-09-07 9:03 ` KAMEZAWA Hiroyuki
2010-09-07 9:45 ` Andi Kleen [this message]
2010-09-07 8:37 ` Minchan Kim
2010-09-07 8:47 ` KAMEZAWA Hiroyuki
2010-09-07 14:51 ` Minchan Kim
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=20100907114538.71fc2dcd@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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