Hi,

Excellent, this will make it _tons_ easier for me to create new zones
of mem_map arrays on the fly to allow us to create struct pages for
PCI IO-aperture memory (necessary for kiobuf mappings of IO memory).

A related question: do you already have an idea how the driver interface
for that could look like? I mean, some drivers need a virtual address,
some need the physical address for dma and some of them might need
bounce buffers. E.g. I don't know how to get (quickly) from a page
struct which represents an io mapping to the physical address. Will we
add some generic funtions for this which can be used by drivers or even
let the drivers only specify its requirements and the buffer code will
generate an appropriate io request. I have a few ideas, but I don't know
if already concrete plans exists.

bye, Roman
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/