Hello everyone,

My name is Kay. I’m a huge "oom-pi" fan, but only recently have been looking at 
from devel perspective.

I appreciate if somebody shows me the entry point into understanding how 
orterun and user program interact, and more importantly how to change the way 
they interact.

The reason: I am making a plugin for MPI support in another message passing 
system. This plugin is loaded from a dynamic library sometime after the process 
is started and is run on a separated tread. Therefore, (1) it does not receive 
any command line arguments, and (2) it is not allowed to use standard pipes 
(file descriptors 0,1, 2). With that in mind, I’de like to interface this 
plugin from inside so-called ARE (which is the name for the runtime environment 
for this particular message passing system) to our old friend ORTE. I have the 
option to run “are” as a user program run by orterun.

$orterun are ./actual-user-program 

 It might be wishful thinking, but I am also kindda hoping that I could get 
orterun out of the way all together by embedding a part of its implementation 
directly inside that plugin.

I’de appreciate to hear your insights.

Best,
— Kay

Reply via email to