linux-kernel - Re: [PATCH/RFCv3 0/6] The Contiguous Memory Allocator framework

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20100820001339N.fujita.tomonori@lab.ntt.co.jp>
Date:	Fri, 20 Aug 2010 00:15:12 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	kyungmin.park@...sung.com
Cc:	m.nazarewicz@...sung.com, linux-mm@...ck.org,
	fujita.tomonori@....ntt.co.jp, dwalker@...eaurora.org,
	linux@....linux.org.uk, corbet@....net, p.osciak@...sung.com,
	broonie@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org,
	hvaibhav@...com, hverkuil@...all.nl, kgene.kim@...sung.com,
	zpfeffer@...eaurora.org, jaeryul.oh@...sung.com,
	linux-media@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	m.szyprowski@...sung.com
Subject: Re: [PATCH/RFCv3 0/6] The Contiguous Memory Allocator framework

On Wed, 18 Aug 2010 12:01:35 +0900
Kyungmin Park <kyungmin.park@...sung.com> wrote:

> Are there any comments or ack?
> 
> We hope this method included at mainline kernel if possible.
> It's really needed feature for our multimedia frameworks.

You got any comments from mm people?

Virtually, this adds a new memory allocator implementation that steals
some memory from memory allocator during boot process. Its API looks
completely different from the API for memory allocator. That doesn't
sound appealing to me much. This stuff couldn't be integrated well
into memory allocator?
--
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/