Contents:
% % THE \simulan LOGO IS DEFINED HERE. % \def\simulan{{\rm s\kern-.06em\raise-.5ex\hbox{i}\kern-.1em\raise-.1ex \hbox{m}\raise-.3ex\hbox{u}\kern-.10emL\kern-.1667em\lower-.6ex \hbox{a}\kern-.10emn}}
%% the \PBeam Logo is defined here \def\PBeam{{\sc\kern.15emP\kern-.9em\raise.125ex\hbox{$\leftarrow$}\sc\kern-.25emB\sc\kern-.1eme\kern-.1ema\kern-.1emm}}
You might also want look at the companion thesis about modelling
with simuLan:
[Schmida91]
Ralf Schmidt-Dannert:
\simulan: Modellierung und Simulation lokaler Netzwerke.
Diplomarbeit, TU Braunschweig, 1991 (in german).
A BiBTeX-File, from my Dissertation.
The system uses a global
virtual name space to provide migration and rollback
transparency in user space for distributed groups of processes
on workstations. Applications always use the same virtual
names for the operating system objects, independent of their
current real location. The system calls are interposed and
their parameters translated between the name spaces. Unlike
other migration mechanisms,
does not require the applications to be written
for a specific programming model or communication library.
The first approach to execute applications in the virtual name
space was to link the programs with a modified system
library. Now, in this paper we describe design and
implementation of a separate system call interposition process
that accesses the application via the debugging
interface. The main advantage of this approach is that it can
handle even unmodified (e.g. commercially bought)
application programs. We compare measured performance figures
with previous similar approaches and the modified system
library.
ISI Accession Number: WOS:000077612600023
2 citations in ISI Web of Science until August 2013