lkml.org 
[lkml]   [2004]   [Jun]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: finish_task_switch high in profiles in 2.6.7
    From
    Date
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:04    [W:2.369 / U:0.324 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site