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]

Date:	Tue, 14 Aug 2007 00:58:41 +0200
From:	Andi Kleen <ak@...e.de>
To:	Christoph Lameter <clameter@....com>
Cc:	Andi Kleen <ak@...e.de>, 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 Mon, Aug 13, 2007 at 03:00:14PM -0700, Christoph Lameter wrote:
> You said that ZONE_DMA will still be there right? So the zone will be 

There will be a (variable sized) dma zone, but not a ZONE_DMA entry in pgdat 
or in the the fallback lists.

> 
> > There are still other architectures that use it. Biggest offender
> > is s390. I'll leave them to their respective maintainers.
> 
> IA64 also uses ZONE_DMA to support 32bit controllers. 

ZONE_DMA32 I thought?  That one is not changed.

> 
> So I think we can only get rid of ZONE_DMA in its 16MB incarnation for 
> i386 and x86_64.

Correct. 

> 
> But you will be keeping ZONE_DMA32?

Yes.

> If so then it may be better to drop ZONE_DMA32 and make ZONE_DMA be below 
> 4GB like other 64bit arches.

That might be possible as a followup, but would change the driver
API. Is it worth it? 

-Andi

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