Kedar Sovani wrote: > > Hi, > And also that unlike the processes can be pre- empted,while the > kernel cannnot. In that particular case you may have performance gains if > you have something in the kernel, rather than being in the user space, as it > runs continuously. I don't think this is a good argument. You must schedule() regularly in order for the machine to be usable. Running in kernel space does not change that; but it means you must call schedule() explicitly. The only thing you save by running in kernel space is the cost of the user<-->kernel transition, which I would expect to be very small (though possibly significant in some application, I suppose). Cheers, -- Joe "I'd rather chew my leg off than maintain Java code, which sucks, 'cause I have a lot of Java code to maintain and the leg surgery is starting to get expensive." - Me -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
