From: Maxim Uvarov <muvarov@ru.mvista.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Performance Stats: Kernel patch
Date: Fri, 11 May 2007 16:55:59 +0000 [thread overview]
Message-ID: <4644A01F.4080501@ru.mvista.com> (raw)
In-Reply-To: <p731whofe73.fsf@bingen.suse.de>
Andi Kleen wrote:
>Maxim Uvarov <muvarov@ru.mvista.com> writes:
>
>
>>This data is useful for detecting hyperactivity
>>patterns between processes.
>>
>>
>
>You need a lot better rationale to slow down these important
>fast paths. Particularly the syscall path is very hot.
>
>Is this something that is really generally useful? The context
>switch counters might be occasionally useful, but strace can
>you just give the syscall count anyways. Still not sure
>it really should go into the standard kernel. Perhaps just keep it
>as a systemtap script?
>
>-Andi
>
>
It is difficult to use strace for multi thread applications to
verify which thread is doing what.
next prev parent reply other threads:[~2007-05-11 12:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 17:19 [PATCH] Performance Stats: Kernel patch Maxim Uvarov
2007-05-10 23:31 ` Andi Kleen
2007-05-11 16:55 ` Maxim Uvarov [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-05 14:43 Maxim Uvarov
2007-06-06 6:38 ` Andrew Morton
2007-06-06 17:29 ` Jay Lan
2007-05-30 18:49 Maxim Uvarov
2007-06-04 19:19 ` Andrew Morton
2007-06-04 19:33 ` Jay Lan
2007-06-04 19:49 ` Jonathan Lim
2007-06-04 20:13 ` Jay Lan
2007-06-05 6:50 ` Balbir Singh
2007-05-22 17:19 Maxim Uvarov
2007-05-22 18:48 ` Dave Jones
2007-05-22 20:08 ` Andrew Morton
2007-05-11 17:13 Maxim Uvarov
2007-05-12 10:39 ` Andrea Righi
[not found] <4625FFCF.8040402@ru.mvista.com>
2007-04-20 4:36 ` [patch] " Andrew Morton
2007-04-25 10:59 ` Maxim Uvarov
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=4644A01F.4080501@ru.mvista.com \
--to=muvarov@ru.mvista.com \
--cc=andi@firstfloor.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox