From: "Chris Friesen" <cfriesen@nortel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
Christoph Lameter <cl@linux.com>,
linux-kernel@vger.kernel.org
Subject: Re: Scheduler regression: Too frequent timer interrupts(?)
Date: Fri, 17 Apr 2009 11:19:04 -0600 [thread overview]
Message-ID: <49E8BA08.8020908@nortel.com> (raw)
In-Reply-To: <20090417164918.GK8253@elte.hu>
Ingo Molnar wrote:
> it's even simpler than that: use a user-space loop and an alert()
> based signal-handler triggered measurement to count the number of
> loops user-space can execute, per second.
Alternately, just measure how long it takes to execute a given (large)
number of loops. This avoids the signal handler.
Chris
next prev parent reply other threads:[~2009-04-17 17:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 19:53 Scheduler regression: Too frequent timer interrupts(?) Christoph Lameter
2009-04-17 7:00 ` Peter Zijlstra
2009-04-17 13:42 ` Christoph Lameter
2009-04-17 14:16 ` Peter Zijlstra
2009-04-17 14:29 ` Christoph Lameter
2009-04-17 14:51 ` Peter Zijlstra
2009-04-17 15:04 ` Christoph Lameter
2009-04-17 15:28 ` Peter Zijlstra
2009-04-23 4:42 ` Pavel Machek
2009-04-28 21:02 ` Christoph Lameter
2009-04-28 21:23 ` Peter Zijlstra
2009-04-28 21:21 ` Christoph Lameter
2009-04-17 15:35 ` Ingo Molnar
2009-04-17 15:55 ` Christoph Lameter
2009-04-17 16:23 ` Peter Zijlstra
2009-04-17 16:33 ` Christoph Lameter
2009-04-17 16:49 ` Ingo Molnar
2009-04-17 17:19 ` Chris Friesen [this message]
2009-04-17 17:45 ` Christoph Lameter
2009-04-17 18:11 ` Peter Zijlstra
2009-04-17 18:20 ` Christoph Lameter
2009-04-17 18:58 ` Peter Zijlstra
2009-04-17 20:34 ` Christoph Lameter
2009-04-17 20:53 ` Peter Zijlstra
2009-04-17 23:24 ` Chris Friesen
2009-04-18 7:35 ` Ingo Molnar
2009-04-18 7:59 ` Andi Kleen
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=49E8BA08.8020908@nortel.com \
--to=cfriesen@nortel.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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.