linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naushit Sakarvadia" <naushit@softhome.net>
To: "Cort Dougan" <cort@fsmlabs.com>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Fw: SMP Support
Date: Fri, 21 Jun 2002 12:18:17 -0500	[thread overview]
Message-ID: <006d01c21947$a34892d0$7402a8c0@QUINTUMCHI.COM> (raw)
In-Reply-To: 20020621103710.C13628@host110.fsmlabs.com


Cort,

Thanks ,
I will definately look into issue of  broadcast TLB invalidate with 755.
But  I want to know  How do the let the Kernel know that there is
another processor sitting on the 60x Bus?

I never worked on SMP based system...I just want to know where to start??

Thanks
Naushit.



> There are some tricks for the 750 on SMP that no-one has actually tried
> yet.  I did some early work with it that ended up with horrible
> performance.  The 750's don't broadcast TLB invalidates and that really
> messes SMP up for us.
>
> I'm not sure of the 755 follows in this tradition but I'd suggest checking
> carefully for that.  SMP works well on anything other than 750's, though.
>
> } I was wondering if there is SMP support  for TWO Processors
> } in Powerpc based Embedded Sytem.
> }
> } I have 2  MPC755 Processors  sharing one 60x Bus.
> } Both of  them have 1MB of L2 Cache, and Share DRAM connected to 60x bus.
> }
> }
> } Have anybody already used powerpc SMP??
> } Have anybody used M-system Disk-on-Chip 2000 with PowerPC linux?
> } How about Powerspan PCI bridge support??
> }
> }
> } Thanks for any pointers
> }
> } Naushit.
> }
> }


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-06-21 17:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 23:40 Fw: SMP Support Naushit Sakarvadia
2002-06-21 16:37 ` Cort Dougan
2002-06-21 17:18   ` Naushit Sakarvadia [this message]

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='006d01c21947$a34892d0$7402a8c0@QUINTUMCHI.COM' \
    --to=naushit@softhome.net \
    --cc=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).