linux-kernel - Re: [RFC][PATCH 1/3] contigous big page allocator

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: <AANLkTik7Gj0M64D8kYoToja3QmmSLMCUQHjVPKibp0Qm@mail.gmail.com>
Date:	Fri, 15 Oct 2010 00:50:49 +0300
From:	Felipe Contreras <felipe.contreras@...il.com>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	andi@...stfloor.org, kamezawa.hiroyu@...fujitsu.com,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	minchan.kim@...il.com
Subject: Re: [RFC][PATCH 1/3] contigous big page allocator

On Thu, Oct 14, 2010 at 6:24 PM, FUJITA Tomonori
<fujita.tomonori@....ntt.co.jp> wrote:
> On Thu, 14 Oct 2010 15:09:13 +0300
> Felipe Contreras <felipe.contreras@...il.com> wrote:
>
>> > As already pointed out, some embeded drivers need physcailly
>> > contignous memory. Currenlty, they use hacky tricks (e.g. playing with
>> > the boot memory allocators). There are several proposals for this like
>> > adding a new kernel memory allocator (from samsung).
>> >
>> > It's ideal if the memory allocator can handle this, I think.
>>
>> Not only contiguous, but sometimes also coherent.
>
> Can you give the list of such drivers?

omapfb and tidspbridge. Perhaps tidspbridge can be modified to flush
the relevant memory, but for now it does. I'm not sure about omapfb,
but it would be very likely that user-space would need to be modified
if flushes suddenly become required.

-- 
Felipe Contreras
--
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/