> > > As a graduation project i intended to make linux distributed
>
> snip
> >
> > >The guest system (where the process originated) would
> > >however have a pseudo process running on it, which would not take much
> > >resources but would help in handling various signals/
> >
> > SSI support cluster wide signaling. That means you can send signal to a
> > process running on other node( you have cluster wide PID )
> >
> The openSSI process model is quite different than Bproc or Mosix or
> your "guest system" proposal. In the openSSI model, there is no
> pseudo or shadow process at the processes creation node; after
> a processes migrates, all its system calls are executed on the new
> node and signalling to the process is done directly to the process on
> the new node. Besides the obvious performance advantages this can
> give, it can also provide availability advantages because the
> creation node can go down without taking the process down with it.
>
Yeah, openSSI approach has some advantages, but how about the other side,
how are the devices and files being handled? isn't it wrong to run
someone elses process when the data that he is supposed to provide is
missing? My work is based on a workstation model where all the nodes are
independent workstations (in most cases with similar configurations, as in
a computer laboratory at a university). One of my major constraints is
that the system should be binary compatible with the kernel that does not
support my model. In my case i plan packing and restarting a process when
the creation node goes down.
Prasad.
> bruce
>
> > -aneesh
> >
-- Failure is not an option- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/