Re: openMosix Question

From: Moritz Franosch (mail_at_Franosch.org)
Date: 07/07/03


Date: 07 Jul 2003 11:42:18 +0200


Noah Roberts <nroberts@dontemailme.com> writes:

> openMosix advertizes itself as not needing any special requirements
> of the programmer

Openmosix even has no programming interface.

> but it is not clear what kind of applications they are
> talking about.

Processes with single threads. These processes may communicate over
the network.

> If openMosix really does make several nodes act like a
> single SMP computer

It does not. This may be a longterm goal of Openmosix. The website is
misleading.

> then there should be no special requirements when
> working with shared memory and threads.

Processes that work with shared memory or use multiple threads can't
be "migrated" to another machine.

> On the other hand I am skeptical that this is actually what is going
> on; it doesn't seem reasonable to expect that memory can be shared
> across nodes,

Why not? Except that Gigabit Ethernet may be too slow.

> which is what would be required of such a system.

> I wish to develop a parallel application that will need to share a
> large amount of data amongst all of its subprocesses. Is it really as
> seamless as the openMosix site leads me to believe or would I still be
> required to deal with the shared memory aspect?

The processes would have to communicate over the network. Look at
libraries (like MPI) for developing parallel applications.

> It would certainly make my life a lot easier to just be able to
> spawn threads and it all magically works,

Unfortunately, no. And even if it worked, it would possibly be (much?)
slower than handcrafted communication designs like you would use with
e.g. MPI.

> but this just doesn't seem like it would work out the way I want.

Moritz

-- 
Dipl.-Phys. Moritz Franosch
http://Franosch.org


Relevant Pages

  • Re: Needing info on passing data between applications. Win[C#]
    ... its been a long time when i used shared memory. ... this is also a very fas way to communicate. ... I am not a friend ...
    (microsoft.public.dotnet.languages.csharp)
  • Approaches of interprocess communication
    ... communicate via TCP/IP if the processes run on the same machine. ... CORBA -- similar to webservices but more complicated to code. ... Supposing both processes are written in Python, ... shared memory sound the most suited approach. ...
    (comp.lang.python)
  • Re: Approaches of interprocess communication
    ... communicate via TCP/IP if the processes run on the same machine. ... sockets, as really bulky SOAP messages need to be passed around. ... CORBA -- similar to webservices but more complicated to code. ... shared memory sound the most suited approach. ...
    (comp.lang.python)
  • Re: shared memory: open + unlink + sendfd + mmap
    ... > I have two processes that need to communicate through shared memory. ... > descriptor to the related process, who then uses the file descriptor ... > I've read about kernel hacks that allow 'sync' to skip files with no ...
    (comp.unix.programmer)