mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Artemio <artemio@artemio.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SMP question
Date: Thu, 12 Jun 2003 08:42:42 +0300	[thread overview]
Message-ID: <200306120841.08809.artemio@artemio.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0306111838360.20310-100000@coffee.psychology.mcmaster.ca>

Hello!

> > I'm building a hard real-time Linux (RTLinux) system on a 2x Xeon
> > machine. If
>
> then LKML is not the place for you.  RTLinux is a fork of "real" linux.

Well, those guys seem to have success on the same machines that I fail. 

I even used *their* .config file to compile a kernel, but I still fail.

> well, talk to the rtlinux people.  considering what rtlinux changes from
> real linux, this hang is not a big surprise.

Yes, rtlinux runs linux kernel as it's idle thread, and it messes up the 
system - I mean it becomes more difficult to make it work if it doesn't work.

> > So, I have to deside between these two:
> >
> >  - Run rtlinux and hard-realtime applications on a kernel without SMP
> > support. How much performance will I loose this way? Is SMP *THAT*
> > critical?
>
> huh?  it's not critical at all.  though if you have two processors,
> you've just wasted several hundred dollars unless you run SMP.

:-)

> >  - Run all tasks in a usual way, no hard realtime, but with SMP support.
>
> why do you think you need rtlinux-type realtime?

Hmm... Nice question.

We are to run many applications that will be mission-critical. That's why we 
decided to make them in hard-realtime.

The other way is probably making low-priority kernel threads by usual means.

But I think hard-realtime will give us more performance. 

> > Also, if I turn hyperthreading off, how will it influence the system with
> > SMP support? Without SMP support?
>
> HT is just hardware-supported multithreading - imagine that you have
> the same old processor, except that the CPU's instruction-dispatcher
> is reading from two instruction streams.  HT doesn't add any new resources,
> just shares a single CPU among two threads.

Got it.

> I suspect the design of rtlinux is inherently incompatible with HT.

I will try turning HT off and running RTLinux.



Thank you very much for your reply!


Artemio.


       reply	other threads:[~2003-06-12  5:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0306111838360.20310-100000@coffee.psychology.mcmaster.ca>
2003-06-12  5:42 ` Artemio [this message]
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
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

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=200306120841.08809.artemio@artemio.net \
    --to=artemio@artemio.net \
    --cc=hahn@physics.mcmaster.ca \
    --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®