Hi, i am not an expert kernel programmer. But I think device drivers should help you solve the problem. But you will have to figure out a mechanism for storing the state from the kernel(i mean the exact control sequence). If it is the networking stack then netfilter is the option - otherwise a naive approach is to change the kernel code and recompile the kernel. But this is not preffered. May be if you tell te exact nature of the information to be stored then someone can suggest that mechanism. The position at which you will re-introduce the information back into the kernel is also problem specific. So I guess we need to know more about the information being handled. -Pradeep On Mon, 28 Jan 2002, Israel Fernandez wrote: > I asked about a kernel function waiting for a user space app, and a guy who knows very mush about the linux kernel give me this answer: > > Split it into two things. Instead of thinking about the kernel module > waiting think about the kernel module remembering enough state on a > queue > somewhere and finishing, then a second set of code execution occurring > when > the user space app makes a second ioctl call with the reply. > > But I don't know how interpret this, please help me.... > -- 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/
