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

On Friday 22 September 2006 06:02, Christoph Lameter wrote:
> We have repeatedly discussed the problems of devices having varying 
> address range requirements for doing DMA.

We already have such an API. dma_alloc_coherent(). Device drivers
are not supposed to mess with GFP_DMA* directly anymore for quite
some time. 

> We would like for the device  
> drivers to have the ability to specify exactly which address range is 
> allowed. 

I actually have my doubts it is a good idea to add that now. The devices
with weird requirements are steadily going away.

-Andi

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

---

• Follow-Ups:
  • 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: Christoph Lameter <[email protected]>

• References:
  • [RFC] Initial alpha-0 for new page allocator API
    • From: Christoph Lameter <[email protected]>

• Prev by Date: removing multiple kfree() and return's
• Next by Date: [BUGFIX][PATCH] cpu to node relationship fixup take2 [1/2] acpi_map_cpu2node
• Previous by thread: [RFC] Initial alpha-0 for new page allocator API
• Next by thread: Re: [RFC] Initial alpha-0 for new page allocator API
• 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]