On Wed, 30 Mar 2005, Muli Ben-Yehuda wrote: > On Wed, Mar 30, 2005 at 09:25:29AM +0200, Shachar Shemesh wrote: > > > Processes should never spend too much time in the "D" state. The very > > fact that certain activities mean you are almost guaranteed to see > > processes in the "D" state means there are bugs in the kernel. > > Why do you think so? D means that a process is holding a lock. Do you > mean "bugs" in the sense of "long lock holding times"?
since when does 'D' state means a process is holding a lock? there are many situations in the kernel that processes are put to sleep while not holding any lock (at least as far as i saw - and i'm talking about 2.6 kernels) - unless the lock-taking was done much, much earlier. by the way, with 'holding a lock', do you also talk about 'having a page from the page cache marked as locked'? -- guy "For world domination - press 1, or dial 0, and please hold, for the creator." -- nob o. dy ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
