Re:Understanding Linux CPU Load - when should you be worried?
by caf on Tuesday July 26, 2011 @08:54PM
(#2810202)
Not all processes blocked on I/O are in D state - for a common example, processes blocked on I/O to a network socket or terminal will simply be in the S state, and not count towards load.
[ Parent
| on HN ]
Re:Understanding Linux CPU Load - when should you be worried?
by duskwuff on Tuesday July 26, 2011 @10:42PM
(#2810487)
In practice, processes typically go into D state ("uninterruptible sleep") when they're blocked on access to a local disk, whether that's explicit I/O (read/write) or implicit (paging). Not coincidentally, this is also the one type of blocking I/O that you can't get knocked out of by a signal.
Re:Understanding Linux CPU Load - when should you be worried?
by freiheit on Wednesday July 27, 2011 @04:20PM
(#2813933)
Actually, they'll get blocked on access to NFS or other network-based disk, too. (but you can configure the NFS mount to allow signals to interrupt) I've seen NFS problems lead to loads over 100.