Logo AND Algorithmique Numérique Distribuée

Public GIT Repository
Add a TODO file with my ideas to make splay work.
authorChristophe Thiéry <christopho128@gmail.com>
Fri, 29 Jul 2011 15:29:19 +0000 (17:29 +0200)
committerChristophe Thiéry <christopho128@gmail.com>
Fri, 29 Jul 2011 15:29:19 +0000 (17:29 +0200)
examples/lua/SimSplay/TODO [new file with mode: 0644]

diff --git a/examples/lua/SimSplay/TODO b/examples/lua/SimSplay/TODO
new file mode 100644 (file)
index 0000000..42dcb7f
--- /dev/null
@@ -0,0 +1,26 @@
+--------------------------------------------
+A few notes abouts what I would like to do
+to make Splay applications work with SimGrid
+--------------------------------------------
+
+Create an executable "simsplay" that runs a Splay Lua script
+with SimGrid.
+
+Ideally, its usage would be:
+
+simsplay platform_file.{xml|lua} deployment_file.{xml|lua} splay_script.lua [simgrid_options...]
+
+I'm not sure about the format of the platform and deployment files yet.
+We could accept both XML and Lua files, since their is a great Lua API to
+describe platforms, or only the XML ones.
+
+The simsplay executable (which is compiled C) would initialize SimGrid, create
+the environment, and for each simulated process, create a new lua_State*
+object that runs the Lua script provided by the user (splay_script.lua in the
+example above).
+
+The current Lua API of SimGrid (3.6) uses Lua coroutines (i.e. sequential,
+lightweight threads) to simulate processes in a single, shared Lua state.
+However, in Splay, the Lua global values must not be shared between simulated
+processes: this is why we need distinct Lua states.
+