[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hurd-bug
Subject:    Re: Revisited: Hurd on a cluster computer
From:       Mark Morgan Lloyd <markMLl.out () telemetry ! co ! uk>
Date:       2017-05-21 14:14:46
Message-ID: fd9d0782-67e7-1e7f-097a-542a1c2273e6 () telemetry ! co ! uk
[Download RAW message or body]

On 21/05/17 13:45, Justus Winter wrote:
> Samuel Thibault <samuel.thibault@gnu.org> writes:

>>> Though there was some work, a reimplementation if memory serves, of the
>>> netmsg servers.  The archive should have some infos on that.

Yes, by Brent who was the instigator of the original thread that I was 
belatedly commenting to :-)

>> Well, that's unrelated to the question above, which was actually
>> unrelated to the original thread, which you are answering now :)
>
> Ah, segmentation... Indeed, I wasn't reading that carefully, I thought
> is was related to the in-kernel forwarding of Mach messages across
> networks...

Which is of course an interesting question in itself, and one which 
entirely by chance a hardware engineer of my acquaintance has been 
casually pondering.

Incidentally, I've also just remembered 
http://www.scalemp.com/products/product-comparison/ which is another 
interesting attempt to build a cluster on top of Linux.

Finally, I'm not entirely sure where IBM mainframe operating systems 
stand on the "SSI or not SSI" question: they have, of course, been doing 
this sort of thing for decades. My understanding is that a single 
computer (i.e. one "frame") is basically SMP with SSI, but that a 
sysplex has multiple OS instances with jobs moved around as required. 
It's perhaps interesting that Moshe Bar, who was originally responsible 
for MOSIX, is occasionally seen hanging out in IBM mainframe mailing lists.

CC not necessary, I'm subscribed.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]

[prev in list] [next in list] [prev in thread] [next in thread]