On Thu, Apr 28, 2011 at 08:22:29AM +0200, Bruno Prémont wrote: > On Wed, 27 Apr 2011 14:55:49 "Paul E. McKenney" wrote: > > On Wed, Apr 27, 2011 at 12:28:37AM +0200, Thomas Gleixner wrote: > > > On Tue, 26 Apr 2011, Linus Torvalds wrote: > > > > Normally SCHED_FIFO runs until it voluntarily gives up the CPU. That's > > > > kind of the point of SCHED_FIFO. Involuntary context switches happen > > > > when some higher-priority SCHED_FIFO process becomes runnable (irq > > > > handlers? You _do_ have CONFIG_IRQ_FORCED_THREADING=y in your config > > > > too), and maybe there is a bug in the runqueue handling for that case. > > > > > > The forced irq threading is only effective when you add the command > > > line parameter "threadirqs". I don't see any irq threads in the ps > > > outputs, so that's not the problem. > > > > > > Though the whole ps output is weird. There is only one thread/process > > > which accumulated CPU time > > > > > > collectd 1605 0.6 0.7 49924 3748 ? SNLsl 22:14 0:14 > > > > I believe that the above is the script that prints out the RCU debugfs > > information periodically. Unless there is something else that begins > > with "collectd" instead of just collectdebugfs.sh. > > No, collectd is a multi-threaded daemon that collects statistics of all > kinds, see http://www.collectd.org/ for details (on my machine it > collects CPU usage, memory usage [just the basics], disk statistics, > network statistics load and a few more) OK, thank you for the info! Thanx, Paul -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
