From: Jes Sorensen <jes@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: How to lock current->signal->tty
Date: Wed, 09 Aug 2006 20:10:48 +0200 [thread overview]
Message-ID: <44DA2528.5010905@sgi.com> (raw)
In-Reply-To: <20060809162440.GA14143@intel.com>
Luck, Tony wrote:
> On Wed, Aug 09, 2006 at 11:44:10AM +0100, Alan Cox wrote:
>> Jes, read up on kprobes a little if you think its of no use in these
>> kind of situations. A systemtap script to count/measure alignment fault
>> rates and see who is causing the load isn't very hard to write.
>
> But this does make sense ... the system administrator of a mainframe or
> super-computer can (and arguably should) be monitoring resource
> utilization and providing feedback to users on how to get the best
> performance from their applications.
Actually perfmon would probably be better suited for this on ia64 than
kprobes/systemtap. You can do it on hackish way with a [jk]probe, but it
isn't going to be all that pretty.
> -Tony (currently at 90% rip out this message, 10% add the mutex lock/unlock).
Nuke it!
Jes
next prev parent reply other threads:[~2006-08-09 18:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 15:17 How to lock current->signal->tty Alan Cox
2006-08-08 15:10 ` Arjan van de Ven
2006-08-08 15:44 ` Alan Cox
2006-08-08 16:41 ` Luck, Tony
2006-08-08 17:50 ` Alan Cox
2006-08-09 8:09 ` Jes Sorensen
2006-08-09 10:44 ` Alan Cox
2006-08-09 11:26 ` Jes Sorensen
2006-08-09 16:24 ` Luck, Tony
2006-08-09 18:10 ` Jes Sorensen [this message]
2006-08-08 22:06 ` Jan Kara
2006-08-08 17:11 ` Stephen Smalley
2006-08-08 17:43 ` Alan Cox
2006-08-08 17:44 ` Stephen Smalley
2006-08-08 18:10 ` Alan Cox
2006-08-08 20:02 ` Stephen Smalley
2006-08-13 21:34 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 4:01 Albert Cahalan
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=44DA2528.5010905@sgi.com \
--to=jes@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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