On Wed, Sep 19, 2001 at 08:10:27AM -0700, Usman S. Ansari wrote: > This was partly due to some design decisions which were taken before > I started on this project. Fair enough. > The amount of data transfered between user and kernel is huge, for > small amount of time now and than. That shouldn't be a problem. Accessing files on a fast RAID disk does the same. > Test in last month or so has proved that this method works very well. > This may or may not be a good design, but this is well understood, in > terms of socket communication. I am sure there are other places where > kernel proper uses this method to talk to user land. As a matter of fact, no. In the past the kerneld module loader was the only program that used a different technique to talk to the kernel (it used a SysV message queue), but right now the way to talk to userland is by using device drivers. I think the reason you're facing so many difficulties is in fact an indication that you're using the wrong way to talk to userland. Erik -- J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department of Electrical Engineering, Faculty of Information Technology and Systems, Delft University of Technology, PO BOX 5031, 2600 GA Delft, The Netherlands Phone: +31-15-2783635 Fax: +31-15-2781843 Email: J.A.K.Mouw@its.tudelft.nl WWW: http://www-ict.its.tudelft.nl/~erik/ - Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ IRC Channel: irc.openprojects.net / #kernelnewbies Web Page: http://www.kernelnewbies.org/
