From: "Sébastien Dugué" <sebastien.dugue@bull.net>
To: john stultz <johnstul@us.ibm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: preempt-rt, NUMA and strange latency traces
Date: Fri, 10 Feb 2006 14:07:45 +0100 [thread overview]
Message-ID: <1139576865.5706.68.camel@frecb000686> (raw)
In-Reply-To: <1139511262.28536.10.camel@cog.beaverton.ibm.com>
On Thu, 2006-02-09 at 10:54 -0800, john stultz wrote:
> >
> > I think it's an RSA1 card, but no certainty here. I don't think
> > the x440 came with the RSA2. Is there a way to check for sure without
> > unplugging everything (It's such a mess of cables behind the box)?
>
> No, you're right, the x445 was the box that could have either RSA1 or
> RSA2. The x440 can only have an RSA1.
>
>
> > Whats the SMI issue with the RSA? Could the RSA generate bursts of SMI
> > that could be enough to freeze the CPUs?
>
> SMIs effectively freeze all cpus while the BIOS code executes. With the
> RSA1, there are two main causes of SMIs:
> 1) Periodic SMI: Which occurs every 15 minutes as the RSA checks various
> hardware status and lasts for ~30ms.
>
> 2) Console Redirection SMIs: This occurs only when you use the console
> redirection feature from the RSA. You'll see ~30ms stalls ~once a second
> while the SMI screen-scrapes the console text buffer and sends it out
> over the serial line.
That must be what I've been hitting in my tests and will check soon.
>
> The console redirection one is easy to avoid: just don't use that
> feature if you care about low latencies. The periodic SMI is more
> difficult to work around. With RSA2 based systems, there is a BIOS
> update that allows you to disable this functionality (and on newer
> systems it ships disabled), however I don't believe there is any such
> feature for the older RSA1 based systems.
I'll have to live with it then.
>
>
> > When I ran those tests I was logged on the RSA (serial line). I will
> > try to run the tests again without being connected when I can manage to
> > get some CPU time (eh! shared machine)...
>
> Yes, not using the console redirection feature will definitly help the
> situation, but there still will be the possibility of ~30ms stalls every
> 15 minutes on the x440.
That's the problem and I'll have to synchronize for a proper window
for running my tests.
Is this SMI thing IBM's eyes only stuff or is it documented somewhere?
Thanks for that valuable info.
Sébastien.
next prev parent reply other threads:[~2006-02-10 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 11:28 Sébastien Dugué
2006-02-08 9:41 ` Steven Rostedt
2006-02-08 10:25 ` Ingo Molnar
2006-02-08 10:47 ` Sébastien Dugué
2006-02-08 10:45 ` Sébastien Dugué
2006-02-08 16:49 ` john stultz
2006-02-09 11:11 ` Sébastien Dugué
2006-02-09 11:26 ` Sébastien Dugué
2006-02-09 18:54 ` john stultz
2006-02-10 13:07 ` Sébastien Dugué [this message]
2006-02-10 19:07 ` Lee Revell
2006-02-09 6:04 ` Lee Revell
2006-02-09 11:24 ` Sébastien Dugué
2006-02-09 20:02 ` Lee Revell
2006-02-10 13:18 ` Sébastien Dugué
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=1139576865.5706.68.camel@frecb000686 \
--to=sebastien.dugue@bull.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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®