linux-kernel - Re: [PATCH 3/4] Embed zone_id information within the zonelist->zones pointer

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: <Pine.LNX.4.64.0708131622380.19910@schroedinger.engr.sgi.com>
Date:	Mon, 13 Aug 2007 16:25:23 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Andi Kleen <ak@...e.de>
cc:	Mel Gorman <mel@...net.ie>, Lee.Schermerhorn@...com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 3/4] Embed zone_id information within the zonelist->zones
 pointer

On Tue, 14 Aug 2007, Andi Kleen wrote:

> > But they use GFP_DMA right now and drivers cannot use DMA32 if they want 
> 
> The way it was originally designed was that they use GFP_DMA32,
> which would map to itself on x86-64, to GFP_DMA on ia64 and to
> GFP_KERNEL on i386. Unfortunately that seems to have bitrotted
> (perhaps I should have better documented it) 

The DMA boundaries are hardware depending. A 4GB boundary 
may not make sense on certain platforms. 

> > to be cross platforms compatible? Doesnt the dma API completely do away 
> > with these things?
> 
> No GFP_DMA32 in my current plan is still there.

AFAIK GFP_DMA32 is a x86_64 special that would be easy to remove. Dealing 
with physical boundaries is current done via the dma interface right? Lets 
keep it there?

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