From: "David Schwartz" <davids@webmaster.com>
To: "Artemio" <artemio@artemio.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: SMP question
Date: Wed, 11 Jun 2003 15:34:44 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMEKNDJAA.davids@webmaster.com> (raw)
In-Reply-To: <200306112313.30903.artemio@artemio.net>
> Hello!
> > > How much performance will I loose this way? Is SMP *THAT* critical?
> >
> > You will lose about half your CPU power.
> Hmmm... So, you mean uni-processor Linux kernel can't see two
> processors as
> one "big" processor?
Don't we wish. No, two processors is two processors.
> > > Also, if I turn hyperthreading off, how will it influence the
> > > system with SMP
> > > support? Without SMP support?
> > In a system with more than one physical CPU, hyperthreading
> > is not that
> > big of a performance boost.
> Okay, I will try turning hyperthreding off and see if RTLinux
> keeps hanging
> the machine.
It sounds like you're experiencing a bug. You can do this kind of testing
to help determine the 'envelope' of the bug (that is, under what
circumstances it appears and under what circumstances it doesn't appear),
however this is not a substitute for fixing the bug. ;)
Even if you find a configuration that doesn't show the bug, you still
should work with the RTLinux guys to track down the bug and get it fixed.
If, for example, it's due to unreliable hardware, turning off hyperthreading
might hide it but it will still be lurking there.
RTLinux might be hanging because of problems with the code you're running.
Thinks like deadlock and priority inversion can become much more obvious in
an SMP machine, but can definitely still happen in a UP machine, just much
less often.
DS
next prev parent reply other threads:[~2003-06-11 22:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 17:43 Artemio
2003-06-11 18:04 ` Tigran Aivazian
2003-06-11 19:38 ` Samuel Flory
2003-06-11 19:52 ` Artemio
2003-06-11 20:14 ` David Schwartz
2003-06-11 20:13 ` Artemio
2003-06-11 22:34 ` David Schwartz [this message]
2003-06-11 22:54 ` J.A. Magallon
2003-06-12 5:37 ` Artemio
2003-06-12 12:49 ` Matt Reppert
2003-06-12 17:25 ` Artemio
2003-06-12 14:02 ` Scott Robert Ladd
2003-06-12 20:59 ` J.A. Magallon
2003-06-11 21:25 ` Zwane Mwaikambo
[not found] <Pine.LNX.4.44.0306111838360.20310-100000@coffee.psychology.mcmaster.ca>
2003-06-12 5:42 ` Artemio
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=MDEHLPKNGKAHNMBLJOLKMEKNDJAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=artemio@artemio.net \
--cc=linux-kernel@vger.kernel.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®