Message-ID: <3A924D8A.FBEAD695@cluster-labs.de>
Date: Tue, 20 Feb 2001 11:57:14 +0100
From: Norbert Roos <norbert.roos@cluster-labs.de>
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: Probs with PCI bus master DMA to user space
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org


Hello!

I think the following is general problem, but i haven't found any
information about that yet..

I'm currently writing a driver which wants to transfer data between main
memory and a PCI device. The data buffers are allocated by the program
which uses the driver and therefore lie in the user space. Pointers to
the data buffers are as usual passed to the driver with read() and
write() calls. The driver then initializes a DMA transfer where the PCI
device is bus master.

The driver of course has to split the transfer into several smaller
ones, because the memory pages which contain the data buffers could be
spread across the complete memory.

Before i can actually start the transfer, i have to make sure that the
pages are not swapped and remain locked during the transfer.

The problem I have is: Is there an efficient way to lock the pages which
are accessed by the DMA?

The program using the driver can't use mlock(), because the program does
not know about DMA transfers somewhere below the driver.

The driver should not use mlock() either, because i think that the
execution of mlock() takes about as long as copying the data directly
with copy_from/to_user(). Additionally, I could not unlock() the memory
after the transfer, because the main program might have locked the same
memory area and wants the memory to remain locked.

So what can i do then?

bye
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/