From: Martin Quinson Date: Wed, 26 Sep 2018 22:58:35 +0000 (+0200) Subject: docs: s/Virtual Platform/Simulated Platform/ X-Git-Tag: v3_21~31 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/9f159d9330c05815626203388772dc0cfa5a1575 docs: s/Virtual Platform/Simulated Platform/ --- diff --git a/docs/source/app_smpi.rst b/docs/source/app_smpi.rst index bd04aa09c3..53e0f23a74 100644 --- a/docs/source/app_smpi.rst +++ b/docs/source/app_smpi.rst @@ -34,7 +34,7 @@ Our goal is to enable the study of **unmodified MPI applications**. Some constructs and features are still missing, but we can probably add them on demand. If you already used MPI before, SMPI should sound very familiar to you: Use smpicc instead of mpicc, and smpirun instead -of mpirun. The main difference is that smpirun takes a :ref:`virtual +of mpirun. The main difference is that smpirun takes a :ref:`simulated platform ` as an extra parameter. For **further scalability**, you may modify your code to speed up your diff --git a/docs/source/img/graphical-toc.svg b/docs/source/img/graphical-toc.svg index de43cf2e8d..a6b617203e 100644 --- a/docs/source/img/graphical-toc.svg +++ b/docs/source/img/graphical-toc.svg @@ -24,9 +24,9 @@ borderopacity="1.0" inkscape:pageopacity="0.0" inkscape:pageshadow="2" - inkscape:zoom="0.49497475" - inkscape:cx="-267.7826" - inkscape:cy="12.793361" + inkscape:zoom="1.979899" + inkscape:cx="196.07267" + inkscape:cy="183.99119" inkscape:document-units="mm" inkscape:current-layer="layer1" showgrid="true" @@ -2400,8 +2400,8 @@ sodipodi:nodetypes="cccccccc" /> + id="a6154" + transform="translate(-0.37797619,-16.630952)"> Virtual Simulated + id="a6149" + transform="translate(-0.52916667)">    The S4U Interface    The SMPI Interface - Describing the Virtual Platform + Describing the Simulated Platform Describing the Experimental Scenario    Configuring SimGrid The SimGrid Models diff --git a/docs/source/intro_concepts.rst b/docs/source/intro_concepts.rst index e827426687..b33ab776a2 100644 --- a/docs/source/intro_concepts.rst +++ b/docs/source/intro_concepts.rst @@ -48,10 +48,10 @@ Any SimGrid study entails the following components: parallel application using for example the MPI interface :ref:`(more info) `. - - The **Virtual Platform**. This is a description of a given + - The **Simulated Platform**. This is a description of a given distributed system (machines, links, disks, clusters, etc). Most of the platform files are written in XML althrough a Lua interface is - under development. SimGrid makes it easy to augment the Virtual + under development. SimGrid makes it easy to augment the Simulated Platform with a Dynamic Scenario where for example the links are slowed down (because of external usage) or the machines fail. You have even support to specify the applicative workload that you want @@ -61,13 +61,13 @@ Any SimGrid study entails the following components: - The application's **Deployment Description**. In SimGrid terminology, the application is an inert set of source files and binaries. To make it run, you have to describe how your application - should be deployed on the virtual platform. You need to specify + should be deployed on the simulated platform. You need to specify which process is mapped on which machine, along with their parameters :ref:`(more info) `. - - The **Platform Models**. They describe how the virtual platform + - The **Platform Models**. They describe how the simulated platform reacts to the actions of the application. For example, they compute - the time taken by a given communication on the virtual platform. + the time taken by a given communication on the simulated platform. These models are already included in SimGrid, and you only need to pick one and maybe tweak its configuration to get your results :ref:`(more info) `. @@ -84,7 +84,7 @@ Here are some questions on which SimGrid is particularly relevant: they contribute to compares to the existing solutions from the literature. - - **Design the best Virtual Platform for a given Application.** + - **Design the best [Simulated] Platform for a given Application.** Tweaking the platform file is much easier than building a new real platform for testing purpose. SimGrid also allows for the co-design of the platform and the application by modifying both of them. @@ -119,7 +119,7 @@ SimGrid Execution Modes Depending on the intended study, SimGrid can be run in several execution modes. **Simulation Mode**. This is the most common execution mode, where you want -to study how your application behaves on the virtual platform under +to study how your application behaves on the simulated platform under the experimental scenario. In this mode, SimGrid can provide information about the time taken by @@ -183,7 +183,7 @@ what you are interested in. You are probably looking for a way to run each computation kernel only once, save on disk the time it takes and some other metadata. This code block can then be skipped in simulation and replaced by a synthetic block using the cached information. The -virtual platform will take this block into account without requesting +simulated platform will take this block into account without requesting the real hosting machine to benchmark it. SimGrid Limits diff --git a/docs/source/platform.rst b/docs/source/platform.rst index b2209b082f..295d23e831 100644 --- a/docs/source/platform.rst +++ b/docs/source/platform.rst @@ -12,5 +12,5 @@

-Describing your Virtual Platform -================================ +Describing your Simulated Platform +================================== diff --git a/docs/source/tuto_s4u.rst b/docs/source/tuto_s4u.rst index 18c43c4131..df2feec376 100644 --- a/docs/source/tuto_s4u.rst +++ b/docs/source/tuto_s4u.rst @@ -143,7 +143,7 @@ That being said, an algorithm alone is not enough to define a simulation: SimGrid is a library, not a program. So you need to define your own ``main()`` function as follows. This function is in charge of creating a SimGrid simulation engine (on line 3), register the actor -functions to the engine (on lines 7 and 8), load the virtual platform +functions to the engine (on lines 7 and 8), load the simulated platform from its description file (on line 11), map actors onto that platform (on line 12) and run the simulation until its completion on line 15. @@ -159,7 +159,7 @@ file. Platform File ............. -Platform files define the virtual platform on which the provided +Platform files define the simulated platform on which the provided application will take place. In contains one or several **Network Zone** |api_s4u_NetZone|_ that contain both |Host|_ and |Link|_ Resources, as well as routing information. diff --git a/docs/source/tuto_smpi.rst b/docs/source/tuto_smpi.rst index 12da31bd2f..3b26c93eb3 100644 --- a/docs/source/tuto_smpi.rst +++ b/docs/source/tuto_smpi.rst @@ -54,7 +54,7 @@ To start using SMPI, you just need to compile your application with ``mpiff``, or with ``smpicxx`` instead of ``mpicxx``. Then, the only difference between the classical ``mpirun`` and the new ``smpirun`` is that it requires a new parameter ``-platform`` with a file describing -the virtual platform on which your application shall run. +the simulated platform on which your application shall run. Internally, all ranks of your application are executed as threads of a single unix process. That's not a problem if your application has @@ -73,7 +73,7 @@ Describing Your Platform ------------------------ As a SMPI user, you are supposed to provide a description of your -virtual platform, that is mostly a set of simulated hosts and network +simulated platform, that is mostly a set of simulated hosts and network links with some performance characteristics. SimGrid provides a plenty of :ref:`documentation ` and examples (in the `examples/platforms `_