Messages in this thread | | | Subject | Re: Communication between user process and kernel modules | Date | Fri, 18 Jan 2008 09:59:07 -0500 | From | "linux-os (Dick Johnson)" <> |
| |
On Fri, 18 Jan 2008, mokhtar wrote:
> > Hi > > What are the different solution to make a user process communicate with a > kernel modules? > > Whatis the the advantages and disadvanteges of each solutions ? >
ioctl() is the universal Unix mechanism for control of drivers (modules). open(), close(), read(), write(), mmap() are the other common methods. Some drivers may use sockets for communications. I such a case, you use setsockopt() to change things.
Drivers can signal user-space processes as well. Such programs use select() and poll().
> > --
Cheers, Dick Johnson Penguin : Linux version 2.6.22.1 on an i686 machine (5588.29 BogoMips). My book : http://www.AbominableFirebug.com/ _
**************************************************************** The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
| |