Symmetric Multiprocessing (SMP) development
 help / color / mirror / Atom feed
From: "Earle R. Nietzel" <nietzel@rhinobox.org>
To: Shreyas Kejariwal <skejariwal@perigee.com>
Cc: linux-smp <linux-smp@vger.kernel.org>
Subject: Re: SMP questions
Date: 19 Jun 2003 23:09:28 +0200	[thread overview]
Message-ID: <1056056968.4757.7.camel@home> (raw)
In-Reply-To: <bcsppo$l3g$1@main.gmane.org>

On Thu, 2003-06-19 at 18:55, Shreyas Kejariwal wrote:
> Thanks Robert.
> 
> Getting back to Q3, as you mentioned, it uses shared bus. So that makes it
> hardware specific.  However, I read that Posix threads can achieve the same
> w/o sharing the bus. Is that correct?
> 
> Can anyone point which dual/SMP processors share memory bus ?
> 

There are some systems that have TLC that are shared between a group fo
processors. This how the Unisys ES7000 system works. It has a 32MB TLC
shared between each group of 4 processors. This allows SMP to scale
better.

Unisys has it where you can assign a group (4 processors) to a
particular process which will make sure that a hit occurs in the TLC and
improves performance for that particular process.

Another tweak they allow is to assign I/O devices to a group so that
I/O's are occuring in the same processor group as well.

> 
> Shreyas
> 
> 
> 
> --
> 
> -----------------------------------------------
> Shreyas Kejariwal
> Perigee LLC
> Tel: 315-453 7842 x 42
> 
> 
> 
> "Robert M. Hyatt" <hyatt@cis.uab.edu> wrote in message
> news:Pine.LNX.4.44.0306191057030.5678-100000@crafty.cis.uab.edu...
> > On Wed, 18 Jun 2003, Shreyas Kejariwal wrote:
> >
> > > Hi everyone,
> > >
> > > I am new to this arena and I have few questions so please help me answer
> > > them.
> > >
> > > 1. Looks like most of the new systems employ SMPs. But do we still have
> > > ASMPs systems ?
> >
> >
> > If you mean "asymmetric multiprocessing" the answer is generally "no".
> > That has pretty much disappeared.  If you mean something like clusters
> > and so forth, then they are going strong but require different
> > programming approaches.
> >
> >
> > >
> > > 2. How can we control the tasks, threads to run on a particular
> processor ?
> >
> > Why would you want to?  This is something the operating system should
> > handle correctly.
> >
> >
> > > Is there a way we can specify ? Take the scenario where there are two
> > > multi-threaded applications. I want all the threads of the App1 to run
> on
> > > Processor, P1 and the threads of the App2 on Processor, P2. Not like
> some
> > > threads of App1 would run on P2 depending on the scheduler.
> > >
> >
> >
> > Most systems support some sort of "processor affinity" stuff, but it is
> > a bad idea in general.  Leave the O/S stuff to the O/S.  It _really_
> > does know better...
> >
> >
> >
> > > 3. How can processors access each other's memory / addr space?
> > >
> >
> > Both processors are connected to the memory sub-system with a common
> > bus.
> >
> >
> >
> > > 4. Digging into the scheduler code, I found that we can either set
> scheduler
> > > policy to be either Round Robin or FIFO. Are there other schedulers
> > > available which use different policy.
> > >
> >
> > What scheduler are you looking at?
> >
> >
> >
> > > 5. I read about Shared and Non-shared Cache. How does L2 gets shared.
> Its on
> > > the die. So does that mean that you have to buy a shared cache board ?
> > >
> >
> > L2 isn't shared on Intel platforms. Each processor has its own L2 cache
> > on chip.  Otherwise, it is shared just like memory is shared, with a
> > common bus connecting it to more than one processor.
> >
> >
> >
> >
> > > I apologize if some of the questions are stupid and outside the scope of
> > > this forum.
> > >
> > > Moreover, pointers to web-resources would be helpful.
> > >
> > > Thanks,
> > > Shreyas
> > >
> > >
> > >
> > >
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> > > the body of a message to majordomo@vger.kernel.org
> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >
> >
> > --
> > Robert Hyatt                    Computer and Information Sciences
> > hyatt@cis.uab.edu               University of Alabama at Birmingham
> > (205) 934-2213                  115A Campbell Hall, UAB Station
> > (205) 934-5473 FAX              Birmingham, AL 35294-1170
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-smp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Earle R. Nietzel <nietzel@rhinobox.org>


  parent reply	other threads:[~2003-06-19 21:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 14:41 SMP questions Shreyas Kejariwal
2003-06-19 16:00 ` Robert M. Hyatt
2003-06-19 16:55   ` Shreyas Kejariwal
2003-06-19 17:18     ` Robert M. Hyatt
2003-06-19 21:09     ` Earle R. Nietzel [this message]
2003-06-19 20:58   ` Eckhard Rüggeberg
2003-06-19 21:20     ` Robert M. Hyatt
2003-06-19 21:58   ` Earle R. Nietzel
2003-06-20  0:45     ` Robert M. Hyatt
2003-06-20  7:20       ` Earle R. Nietzel

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=1056056968.4757.7.camel@home \
    --to=nietzel@rhinobox.org \
    --cc=linux-smp@vger.kernel.org \
    --cc=skejariwal@perigee.com \
    /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