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

On Fri, 22 Sep 2006, Andi Kleen wrote:

> Looks like a good start. Surprising how little additional code it is.

Gosh. I just looked at x86_64 dma_alloc_coherent. There is mind boogling 
series of tricks with __GFP_DMA and GFP_DMA32 going on. Could you get me a 
patch that sorts this out if we have alloc_pages_range()? I would expect 
that the will become much simpler.
-
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:
  • [RFC] Initial alpha-0 for new page allocator API
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] Initial alpha-0 for new page allocator API
    • From: Martin Bligh <[email protected]>
  • Re: [RFC] Initial alpha-0 for new page allocator API
    • From: Christoph Lameter <[email protected]>
  • Re: [RFC] Initial alpha-0 for new page allocator API
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: [RETRY] [PATCH] load_module: no BUG if module_subsys uninitialized
• Next by Date: RE: The GPL: No shelter for the Linux kernel?
• Previous by thread: Re: [RFC] Initial alpha-0 for new page allocator API
• Next by thread: More thoughts on getting rid of ZONE_DMA
• 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]