From: Thomas Gleixner <tglx@linutronix.de>
To: dwalker@mvista.com
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc7-rt1
Date: Fri, 26 Aug 2005 08:43:17 +0200 [thread overview]
Message-ID: <1125038597.20120.147.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <1125018945.14592.15.camel@dhcp153.mvista.com>
On Thu, 2005-08-25 at 18:15 -0700, Daniel Walker wrote:
> On Fri, 2005-08-26 at 02:22 +0200, Thomas Gleixner wrote:
> > On Thu, 2005-08-25 at 16:29 -0700, Daniel Walker wrote:
> > > Devastating latency on a 3Ghz xeon .. Maybe the raw_spinlock in the
> > > timer base is creating a unbounded latency?
> >
> > The lock is only held for really short periods. The only possible long
> > period would be migration of timers from a dead hotplug cpu to another.
> > I guess thats not the case.
> >
> > Do you have HIGH_RES_TIMERS enabled ?
>
> No. The cascade has a very long worst case.
You mean the cascading from the outer to the inner wheels ? That should
only happen with tons of active timers.
tglx
next prev parent reply other threads:[~2005-08-26 6:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 6:26 2.6.13-rc7-rt1 Ingo Molnar
2005-08-25 15:36 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-25 17:45 ` 2.6.13-rc7-rt1 Ingo Molnar
2005-08-25 21:35 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-26 6:31 ` 2.6.13-rc7-rt1 Ingo Molnar
2005-08-26 14:27 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-25 17:37 ` 2.6.13-rc7-rt1 Chuck Harding
2005-08-25 21:46 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-25 21:54 ` 2.6.13-rc7-rt1 Ingo Molnar
2005-08-25 22:11 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-25 22:19 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-26 6:32 ` 2.6.13-rc7-rt1 Ingo Molnar
2005-08-25 23:29 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-26 0:22 ` 2.6.13-rc7-rt1 Thomas Gleixner
2005-08-26 1:15 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-26 6:43 ` Thomas Gleixner [this message]
2005-08-26 14:17 ` 2.6.13-rc7-rt1 Daniel Walker
2005-08-26 6:17 ` 2.6.13-rc7-rt1 Ingo Molnar
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=1125038597.20120.147.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®