From: Iain McClatchie <iain@10xinc.com>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: SMP Theory (was: Re: Interesting analysis of linux kernel threading by IBM)
Date: Tue, 25 Jan 2000 11:39:04 -0800 [thread overview]
Message-ID: <388DFBD8.5A89B100@10xinc.com> (raw)
One of the problems with this forum is that you can't hear the murmur
of assent ripple through the hardware design crowd when Larry rants
about this stuff. Larry has had his head out of the box for a long
time.
Look at the ASCI project. The intention was for SGI to build an
Origin with around 1000 CPUs. That Origin had extra cache coherence
directory RAM and special encodings in that RAM so that the hardware
could actually keep the memory across all 1000 CPUs coherent. We
added extra physical address bits to the R10K to make this machine
possible.
Last I heard, the machine is mostly programmed with message passing.
I remember having a talk with an O/S guy who was implementing some
sort of message delivery utility inside the O/S. This was when
Cellular IRIX was in development, and they were investigating having
the various O/S images talk to each other with messages across the
shared memory. Then someone found out the O/S images could signal
each other FASTER through the HIPPI connections than they could
through shared memory. That is, this machine had a HIPPI port local
to each O/S image, and all those HIPPI ports were connected together
via a HIPPI switch.
Those HIPPI connections were build with the _same_physical_link_ as
the shared memory - an 800 MB/s source-synchronous channel. But if
you're sending a message, it's better to have the I/O system just
send the bits one way than have the shared memory system do two round
trips, one to invalidate the mailbox buffer for writing and another to
process the remote cache miss to receive the message.
-Iain McClatchie
www.10xinc.com
iain@10xinc.com
650-364-0520 voice
650-364-0530 FAX
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-01-25 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-25 19:39 Iain McClatchie [this message]
[not found] ` <388DFF0F.8E7784A1@timpanogas.com>
2000-01-25 21:26 ` SMP Theory (was: Re: Interesting analysis of linux kernel threading by IBM) Iain McClatchie
[not found] <000f01bf66da$872a6730$021d85d1@youwant.to>
2000-01-25 10:47 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2000-01-24 22:46 dg50
2000-01-24 23:56 ` Jamie Lokier
2000-01-25 2:38 ` Ralf Baechle
2000-01-25 0:54 ` Larry McVoy
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=388DFBD8.5A89B100@10xinc.com \
--to=iain@10xinc.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=lm@bitmover.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