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 ?
--
View this message in context: http://www.nabble.com/Communication-between-user-process-and-kernel-modules-tp14947386p14947386.html
Sent from the linux-kernel mailing list archive at Nabble.com.
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 [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
Other means of communications include sysfs and procfs. These have the advantage of supporting scripting and can survive ABI changes that can plague the other interfaces; but are meant for low-bandwidth or out-of-band configuration or simple status reporting.
Sincerely -- Mark Salyzyn
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> linux-os (Dick Johnson)
> Sent: Friday, January 18, 2008 9:59 AM
> To: mokhtar
> Cc: [email protected]
> Subject: Re: Communication between user process and kernel modules
>
>
> 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 [email protected] - and destroy
> all copies of this information, including any attachments,
> without reading or disclosing them.
>
> Thank you.
> --
> 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/
>
What about netlink ?
--
View this message in context: http://www.nabble.com/Communication-between-user-process-and-kernel-modules-tp14947386p15016744.html
Sent from the linux-kernel mailing list archive at Nabble.com.