linux-kernel - Re: [RFC] Initial alpha-0 for new page allocator API

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: <4514441E.70207@mbligh.org>
Date:	Fri, 22 Sep 2006 13:14:22 -0700
From:	Martin Bligh <mbligh@...igh.org>
To:	Andi Kleen <ak@...e.de>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Christoph Lameter <clameter@....com>, akpm@...gle.com,
	linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>,
	James Bottomley <James.Bottomley@...eleye.com>,
	linux-mm@...ck.org
Subject: Re: [RFC] Initial alpha-0 for new page allocator API


> And is fine with 16MB anyways I think.
> 
> 
>>- Some aacraid, mostly only for control structures. Those found on 64bit
>>are probably fine with slow alloc.
> 
> 
> That is the only case where there are rumours they are not fine with 16MB.
> 
> 
>>- Broadcom stuff - not sure if 30 or 31bit, around today and on 64bit
> 
> 
> b44 is 30bit. That's true. I even got one here.
> 
> But it doesn't count really because we can handle it fine with existing 
> 16MB GFP_DMA

The problem is that GFP_DMA does not mean 16MB on all architectures.

M.
-
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/