From: Christoph Lameter <cl@linux.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: Scheduler regression: Too frequent timer interrupts(?)
Date: Fri, 17 Apr 2009 16:34:47 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0904171629470.26593@qirst.com> (raw)
In-Reply-To: <1239994719.23397.4979.camel@laptop>
On Fri, 17 Apr 2009, Peter Zijlstra wrote:
> > often must occur in parallel on multiple cores. Processing is delayed if
> > any of the cores encounters a delay due to OS noise.
>
> So you have hard deadlines in the order of us? Are these SCHED_FIFO
> tasks or SCHED_OTHER?
SCHED_FIFO has the effect of removing all the involuntary context switches
but it does not effect the other interrutions.
> Your Xeon is a core2 class machine and should have relatively stable
> TSC, however its also a dual socket, which I think defeats the
> stable-ness.
> What clocksource do you have?
>
> cat /sys/devices/system/clocksource/clocksource0/current_clocksource
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
> Also, looking over the rest of the scheduler tick code, I can't really
> see what would be so expensive.
The expensiveness may be fine if we can limit the number of occurences.
Maybe the histograms for those releases give more insight.
next prev parent reply other threads:[~2009-04-17 20:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 19:53 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
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 [this message]
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=alpine.DEB.1.10.0904171629470.26593@qirst.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®