Re: [PATCH] New phys_addr() syscall

Jamie Lokier (lkd@tantalophile.demon.co.uk)
Mon, 20 Jul 1998 03:08:51 +0100


> Alan Cox writes:
> DMA doesnt honour the MMU write protect bits for copy on write, or for
> page locking. Nor does it set the dirty bit on page table entries.

And you can't get larger contiguous or aligned regions if the device
needs them.

BTW, I'm also doing userspace DMA things (similar to U-net). The driver
I'm using does exactly this. It's mingled with a lot of other junk
though and it's quite buggy, sorry I can't pass it on :-)

I agree with what Alan says in another message, a driver that kmallocs
and maps the memory to user space is a lot saner, not least because the
driver has proper control over the type of memory (GFP_DMA if needed,
for example, and none of the complications of normal user pages).

People may peek at the sound code for an example of mmaping pages used
for DMA.

-- Jamie

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html