linux-kernel - Re: [RFC][PATCH] big continuous memory allocator v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87occa9fla.fsf@basil.nowhere.org>
Date:	Tue, 07 Sep 2010 09:29:21 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	"linux-mm\@kvack.org" <linux-mm@...ck.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	"minchan.kim\@gmail.com" <minchan.kim@...il.com>,
	Mel Gorman <mel@....ul.ie>,
	"kosaki.motohiro\@jp.fujitsu.com" <kosaki.motohiro@...fujitsu.com>
Subject: Re: [RFC][PATCH] big continuous memory allocator v2

KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> writes:

> This is a page allcoator based on memory migration/hotplug code.
> passed some small tests, and maybe easier to read than previous one.

Maybe I'm missing context here, but what is the use case for this?

If this works well enough the 1GB page code for x86, which currently
only supports allocating at boot time due to the MAX_ORDER problem,
could be moved over to runtime allocation. This would make
GB pages a lot nicer to use.

I think it would still need declaring a large moveable
area at boot right? (but moveable area is better than
prereserved memory)

On the other hand I'm not sure the VM is really up to speed
in managing such large areas.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/