On Sun, Mar 10, 2002 at 05:51:33AM -0600, pwa wrote: > > I do not see why this is a problem since spinlocks are SMP only. > I thought the scheduler (called e.g implicetly by a timer interrupt) would > eventually make the process holding the spinlock runable. Then this process > would release the spinlock, and the busy waiting process wold enter the > critical region? Interrupt control path will not call scheduler, but while returning a check is made whether the interrupted control path was either user mode or VM86 mode. If neither the scheduler is bypassed. Regards, Sourav > > > > > _____________________________________________ > Free email with personality! Over 200 domains! > http://www.MyOwnEmail.com > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
