linux-os (Dick Johnson <linux-os <at> analogic.com> writes:
[snip]
> If your program(s) rely upon being in some physical location,
> they are broken. Even with mlockall(), you just keep them
> where they are, not where you'd like them to be. If you
> are trying to DMA into/out-of user-space, there is only
> ONE way to do it. Your driver allocates DMA-able pages and
> your code mmaps() it into user-space. That way, the page(s)
> are always present and have the right attributes. If you
> malloc() something, then try to "convert" in the kernel
> through your driver, the code's broken.
And all this page-moving for getting contiguous DMA memory, happens today on
x86_64 kernels?
Can you please give me a pointer to the source code?
Thanks
-
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/
[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]
