RE: [Patch] Allocate sparse vmemmap block above 4G

On Fri, 9 Nov 2007, Zou, Nanhai wrote:

> > More magic values, both the 4GiB address here and the magic "1" at the
> > end are problems.
> > 
> Yes, the 4UL*1024*1024*1024 could be a define here.

The 4GB boundary here is MAX_DMA32_ADDRESS I guess? We are only having 
this problem because of the two DMA zones on x86_64. I thought Andi was 
getting rid of the first one at 16MB. If he would do so then ZONE_DMA 
could be used instead of DMA32 and everything will be fine.

For now you may want to put

#ifdef CONFIG_ZONE_DMA32

around this code since it depends on DMA32.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [Patch] Allocate sparse vmemmap block above 4G
    • From: Zou Nan hai <[email protected]>
  • Re: [Patch] Allocate sparse vmemmap block above 4G
    • From: [email protected] (Mel Gorman)
  • RE: [Patch] Allocate sparse vmemmap block above 4G
    • From: "Zou, Nanhai" <[email protected]>

• Prev by Date: Re: Some interesting observations when trying to optimize vmstat handling
• Next by Date: [PATCH] Add quirk to set AHCI mode on ICH boards
• Previous by thread: RE: [Patch] Allocate sparse vmemmap block above 4G
• Next by thread: Re: [Patch] Allocate sparse vmemmap block above 4G
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]