Messaging between kernel modules and User Apps
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Zwane Mwaikambo
Quoted 3 lines
The de facto standard for network devices is to use sockets. For character and and block devices Unix/Linux uses the open/poll/ioctl/read mechanisms.
That sounds fine, but..
Quoted 2 lines
You could send your module a pid via proc and have it send a signal to your application as a result of an event.
... please don't even entertain such sick ideas.
Especially when there is fcntl(F_{G,S}ET{OWN,SIG}) infrastructure in
place - kill_fasync().
Quoted 7 lines · Ihar 'Philips' Filipau
Quoted 6 lines · Zwane Mwaikambo
Quoted 3 lines
The de facto standard for network devices is to use sockets. For character and and block devices Unix/Linux uses the open/poll/ioctl/read mechanisms.
That sounds fine, but..
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
You could send your module a pid via proc and have it send a signal to your application as a result of an event.
... please don't even entertain such sick ideas.
Especially when there is
fcntl(F_{G,S}ET{OWN,SIG})infrastructure in
place -kill_fasync().
Just getting 'even' for the last time I advised poll()/ioctl() and I was pummeled with "No... use /proc"! Of course the "best" method is to open a file in the kernel module and have the user poll for a change in length ->;^;<-)
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.