On Fri, Apr 26, 2002 at 03:44:16PM -0600, Trevor Hamm wrote: > - Some threads (ie, kjournald, nfsd) grab the big kernel lock, and some > don't (keventd, kswapd, bdflush). Under what conditions, if any, would > this be necessary? What resources is this lock trying to protect? I remember this being asked on lkml, to a deafening silence. Nobody seems to know. > - Sometimes (quite often, actually) the caller of kernel_thread() blocks > on some kind of wait queue or semaphore, and the kernel thread wakes it > up after some amount of processing (usually before the endless loop in > my general procedure above). Why is this done, and what could happen if > the caller was just allowed to continue on after calling > kernel_thread()? I assume that depends on each situation, there's no general reason for this. > If anyone can direct me to any documentation that addresses these > issues, I would be grateful. Or if anyone can answer some of the I'm afraid as usual, there isn't any. regards john -- "here's a joke for you: why did the chicken turn around and around in circles. as i think she turned around; but why? why did the chicken cross the road; i think she turned around but why? why did the chicken turn around and do something else?" - Mega HAL -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
