From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: finish_task_switch high in profiles in 2.6.7
Date: Thu, 24 Jun 2004 18:44:16 +0800 [thread overview]
Message-ID: <20040624104416.GB8798@outblaze.com> (raw)
In-Reply-To: <m3n02tz203.fsf@averell.firstfloor.org>
> How many context switches do you get in vmstat?
Mentioned in a subsequent message
http://marc.theaimsgroup.com/?l=linux-kernel&m=108806991921498&w=2
> 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.
Hmm, Is there a way to determine which syscall would be the culprit. I
guess this is where something like DTrace would be invaluable
http://www.sun.com/bigadmin/content/dtrace/
next prev parent reply other threads:[~2004-06-24 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ayz2-1Um-15@gated-at.bofh.it>
2004-06-24 10:25 ` finish_task_switch high in profiles in 2.6.7 Andi Kleen
2004-06-24 10:44 ` Yusuf Goolamabbas [this message]
2004-06-24 11:36 ` Andi Kleen
2004-06-24 14:05 ` William Lee Irwin III
2004-06-24 21:22 ` William Lee Irwin III
2004-06-24 21:56 ` William Lee Irwin III
2004-06-25 6:51 ` William Lee Irwin III
2004-06-24 9:15 Yusuf Goolamabbas
2004-06-24 9:27 ` Nick Piggin
2004-06-24 9:34 ` Yusuf Goolamabbas
2004-06-24 9:45 ` Nick Piggin
2004-06-24 10:05 ` Yusuf Goolamabbas
2004-06-24 10:10 ` Nick Piggin
2004-06-24 14:30 ` William Lee Irwin III
2004-06-24 15:33 ` William Lee Irwin III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040624104416.GB8798@outblaze.com \
--to=yusufg@outblaze.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.