malloc pages map to user space

[Eric Saint-Etienne]

> If your kernel module creates a device in /dev that implements the
> mmap method, then you don't need to worry about mucking around with
> vm_maps and objects and whatnot.  Your mmap method just needs to be
> able to convert offsets into the device into physical memory
> addresses,

Yes I'm aware of this facility, thank you.

> and the vm infrastructure will do the rest for you.

Since this mapping is on the main path of the driver, I'm worried that
the overhead on each access of a page fault and a function call (the
pager associated with a cdev mmap) is too much to bear.

So I'd like to do it the "hard" way which I feel is the most optimized.

Thanks!