Messages in this thread | | | Subject | Re: finish_task_switch high in profiles in 2.6.7 | From | Andi Kleen <> | Date | Thu, 24 Jun 2004 12:25:32 +0200 |
| |
Yusuf Goolamabbas <yusufg@outblaze.com> writes:
> Hi, I have a fairly busy mailserver which also has a simple iptables > ruleset (blocking some IP's) running 2.6.7 with the deadline i/o > scheduler. vmstat was reporting that system time was around 80%. I did > the following
How many context switches do you get in vmstat?
Most likely you just have far too many of them. readprofile will attribute most of the cost to finish_task_switch, because that one reenables the interrupts (and the profiling only works with interrupts on)
Too many context switches are usually caused by user space.
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |