Hopefully, the title says it all. I'm looking for a mechanism by which a device driver can respond to a user space processe's read() call by copying data directly into the user space process's address space directly, without using copy_to_user(). The user space process memory is guaranteed to be mlock()ed before read() is called, so paging won't be an issue. Any suggestions? What should the drivers fops->read() function look like in this regard? I would like keep the read() semantics in the user space process. Thanks, stuart. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
