Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Justin Carlson <carlson@sibyte.com>
To: "Matthew Dharm" <mdharm@momenco.com>
Cc: <linux-mips@oss.sgi.com>
Subject: RE: Multiple processor support?
Date: Fri, 23 Mar 2001 16:08:13 -0800	[thread overview]
Message-ID: <01032316143609.00779@plugh.sibyte.com> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIKELLCAAA.mdharm@momenco.com>

On Fri, 23 Mar 2001, Matthew Dharm wrote:
> Well, I'd like to know about both, frankly.  Tho I'm more interested
> in whichever is designed to run on RM7000 series processors.

To the best of my knowledge, the mips64 tree only works in SMP on the ip-27
which is r10K based.  There would be a bit of work to get an RM7K  based
multiprocessor system to run. A fair amount of the "generic" code in
that tree is also pretty ip-27 specific, and so would need to be cleaned up.

I'm working on mips32 SMP support at the moment; there are no existing ports of
this tree to an SMP platform.  The mips64 stuff is certainly much, much more 
mature.  I don't know of any reasons not to use the mips64 side for an RM7K.

-Justin

WARNING: multiple messages have this Message-ID (diff)
From: Justin Carlson <carlson@sibyte.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: linux-mips@oss.sgi.com
Subject: RE: Multiple processor support?
Date: Fri, 23 Mar 2001 16:08:13 -0800	[thread overview]
Message-ID: <01032316143609.00779@plugh.sibyte.com> (raw)
Message-ID: <20010324000813.bCFNQVpWeleHGAPZweVnHK6eAEINRcdOQHAqrFsMiy0@z> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIKELLCAAA.mdharm@momenco.com>

On Fri, 23 Mar 2001, Matthew Dharm wrote:
> Well, I'd like to know about both, frankly.  Tho I'm more interested
> in whichever is designed to run on RM7000 series processors.

To the best of my knowledge, the mips64 tree only works in SMP on the ip-27
which is r10K based.  There would be a bit of work to get an RM7K  based
multiprocessor system to run. A fair amount of the "generic" code in
that tree is also pretty ip-27 specific, and so would need to be cleaned up.

I'm working on mips32 SMP support at the moment; there are no existing ports of
this tree to an SMP platform.  The mips64 stuff is certainly much, much more 
mature.  I don't know of any reasons not to use the mips64 side for an RM7K.

-Justin

  parent reply	other threads:[~2001-03-24  0:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23 22:53 Multiple processor support? Matthew Dharm
2001-03-23 22:58 ` Justin Carlson
2001-03-24  0:01   ` Matthew Dharm
2001-03-24  0:01     ` Matthew Dharm
2001-03-24  0:08     ` Justin Carlson [this message]
2001-03-24  0:08       ` Justin Carlson
2001-03-24  0:29       ` Keith M Wesolowski
2001-03-24  0:40       ` Kevin D. Kissell
2001-03-24  0:40         ` Kevin D. Kissell
2001-03-24  1:23         ` Ralf Baechle
2001-03-24  1:23           ` Ralf Baechle
2001-03-26 19:20         ` Jun Sun
2001-03-29  9:16           ` Kevin D. Kissell
2001-03-29  9:16             ` Kevin D. Kissell
2001-03-24  0:13     ` Joe George

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=01032316143609.00779@plugh.sibyte.com \
    --to=carlson@sibyte.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=mdharm@momenco.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