<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/>
    <title>Project-Team:STORM</title>
    <link rel="stylesheet" href="../static/css/raweb.css" type="text/css"/>
    <meta name="description" content="Research Program - Parallel Computing and Architectures"/>
    <meta name="dc.title" content="Research Program - Parallel Computing and Architectures"/>
    <meta name="dc.subject" content=""/>
    <meta name="dc.publisher" content="INRIA"/>
    <meta name="dc.date" content="(SCHEME=ISO8601) 2019-01"/>
    <meta name="dc.type" content="Report"/>
    <meta name="dc.language" content="(SCHEME=ISO639-1) en"/>
    <meta name="projet" content="STORM"/>
    <script type="text/javascript" src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-MML-AM_CHTML">
      <!-- MathJax -->
    </script>
    <script type="text/javascript" src="../static/js/piwik.js">
      <!-- Piwik JS -->
    </script>
    <noscript>
      <p>
        <img src="https://piwik.inria.fr/matomo.php?idsite=49&amp;rec=1" style="border:0;" alt=""/>
      </p>
      <!-- Piwik Img -->
    </noscript>
  </head>
  <body>
    <div class="tdmdiv">
      <div class="logo">
        <a href="http://www.inria.fr">
          <img style="align:bottom; border:none" src="../static/img/icons/logo_INRIA-coul.jpg" alt="Inria"/>
        </a>
      </div>
      <div class="TdmEntry">
        <div class="tdmentete">
          <a href="uid0.html">Project-Team Storm</a>
        </div>
        <span>
          <a href="uid1.html">Team, Visitors, External Collaborators</a>
        </span>
      </div>
      <div class="TdmEntry">
        <a href="./uid3.html">Overall Objectives</a>
      </div>
      <div class="TdmEntry">Research Program<ul><li class="tdmActPage"><a href="uid8.html&#10;&#9;&#9;  ">Parallel Computing and Architectures</a></li><li><a href="uid9.html&#10;&#9;&#9;  ">Scientific and Societal Stakes</a></li><li><a href="uid10.html&#10;&#9;&#9;  ">Towards More Abstraction</a></li></ul></div>
      <div class="TdmEntry">Application Domains<ul><li><a href="uid12.html&#10;&#9;&#9;  ">Application domains benefiting from HPC</a></li><li><a href="uid18.html&#10;&#9;&#9;  ">Application in High performance computing/Big Data</a></li></ul></div>
      <div class="TdmEntry">
        <a href="./uid20.html">Highlights of the Year</a>
      </div>
      <div class="TdmEntry">New Software and Platforms<ul><li><a href="uid23.html&#10;&#9;&#9;  ">Chameleon</a></li><li><a href="uid28.html&#10;&#9;&#9;  ">hwloc</a></li><li><a href="uid34.html&#10;&#9;&#9;  ">KaStORS</a></li><li><a href="uid38.html&#10;&#9;&#9;  ">KStar</a></li><li><a href="uid43.html&#10;&#9;&#9;  ">AFF3CT</a></li><li><a href="uid49.html&#10;&#9;&#9;  ">MORSE</a></li><li><a href="uid52.html&#10;&#9;&#9;  ">SwLoc</a></li><li><a href="uid55.html&#10;&#9;&#9;  ">VITE</a></li><li><a href="uid59.html&#10;&#9;&#9;  ">PARCOACH</a></li><li><a href="uid65.html&#10;&#9;&#9;  ">StarPU</a></li></ul></div>
      <div class="TdmEntry">New Results<ul><li><a href="uid71.html&#10;&#9;&#9;  ">Multi-Valued Expression Analysis for Collective Checking</a></li><li><a href="uid72.html&#10;&#9;&#9;  ">Hiding the latency of MPI communication</a></li><li><a href="uid73.html&#10;&#9;&#9;  ">Performance monitoring and Steering Framework</a></li><li><a href="uid74.html&#10;&#9;&#9;  ">Heterogeneous task scheduling</a></li><li><a href="uid75.html&#10;&#9;&#9;  ">Task scheduling with memory constraints</a></li><li><a href="uid76.html&#10;&#9;&#9;  ">Leveraging compiler analysis for task scheduling</a></li><li><a href="uid77.html&#10;&#9;&#9;  ">Failure Tolerance for StarPU</a></li><li><a href="uid78.html&#10;&#9;&#9;  ">Static and Dynamic Adaptation of Task parallelism</a></li><li><a href="uid79.html&#10;&#9;&#9;  ">AFF3CT</a></li><li><a href="uid80.html&#10;&#9;&#9;  ">Matlab API for AFF3CT</a></li><li><a href="uid81.html&#10;&#9;&#9;  ">InKS framework</a></li><li><a href="uid82.html&#10;&#9;&#9;  ">HPC Big Data Convergence</a></li><li><a href="uid83.html&#10;&#9;&#9;  ">Hierarchical Tasks</a></li><li><a href="uid84.html&#10;&#9;&#9;  ">ADT Gordon</a></li><li><a href="uid85.html&#10;&#9;&#9;  ">StarPU in Julia</a></li><li><a href="uid86.html&#10;&#9;&#9;  ">Simulation of OpenMP task based programs</a></li><li><a href="uid87.html&#10;&#9;&#9;  ">OpenMP enabled version of Chameleon</a></li></ul></div>
      <div class="TdmEntry">Bilateral Contracts and Grants with Industry<ul><li><a href="uid89.html&#10;&#9;&#9;  ">Bilateral Contracts with Industry</a></li></ul></div>
      <div class="TdmEntry">Partnerships and Cooperations<ul><li><a href="uid94.html&#10;&#9;&#9;  ">Regional Initiatives</a></li><li><a href="uid99.html&#10;&#9;&#9;  ">National Initiatives</a></li><li><a href="uid134.html&#10;&#9;&#9;  ">European Initiatives</a></li><li><a href="uid175.html&#10;&#9;&#9;  ">International Initiatives</a></li><li><a href="uid184.html&#10;&#9;&#9;  ">International Research Visitors</a></li></ul></div>
      <div class="TdmEntry">Dissemination<ul><li><a href="uid188.html&#10;&#9;&#9;  ">Promoting Scientific Activities</a></li><li><a href="uid210.html&#10;&#9;&#9;  ">Teaching - Supervision - Juries</a></li><li><a href="uid266.html&#10;&#9;&#9;  ">Popularization</a></li></ul></div>
      <div class="TdmEntry">
        <div>Bibliography</div>
      </div>
      <div class="TdmEntry">
        <ul>
          <li>
            <a id="tdmbibentyear" href="bibliography.html">Publications of the year</a>
          </li>
        </ul>
      </div>
    </div>
    <div id="main">
      <div class="mainentete">
        <div id="head_agauche">
          <small><a href="http://www.inria.fr">
	    
	    Inria
	  </a> | <a href="../index.html">
	    
	    Raweb 
	    2019</a> | <a href="http://www.inria.fr/en/teams/storm">Presentation of the Project-Team STORM</a> | <a href="https://team.inria.fr/storm/">STORM Web Site
	  </a></small>
        </div>
        <div id="head_adroite">
          <table class="qrcode">
            <tr>
              <td>
                <a href="storm.xml">
                  <img style="align:bottom; border:none" alt="XML" src="../static/img/icons/xml_motif.png"/>
                </a>
              </td>
              <td>
                <a href="storm.pdf">
                  <img style="align:bottom; border:none" alt="PDF" src="IMG/qrcode-storm-pdf.png"/>
                </a>
              </td>
              <td>
                <a href="../storm/storm.epub">
                  <img style="align:bottom; border:none" alt="e-pub" src="IMG/qrcode-storm-epub.png"/>
                </a>
              </td>
            </tr>
            <tr>
              <td/>
              <td>PDF
</td>
              <td>e-Pub
</td>
            </tr>
          </table>
        </div>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid3.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid9.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
      <div id="textepage">
        <!--DEBUT2 du corps du module-->
        <h2>Section: 
      Research Program</h2>
        <h3 class="titre3">Parallel Computing and Architectures</h3>
        <p>Following the current trends of the evolution of HPC systems architectures,
it is expected that future Exascale systems (i.e. Sustaining <span class="math"><math xmlns="http://www.w3.org/1998/Math/MathML"><msup><mn>10</mn><mn>18</mn></msup></math></span> flops)
will have millions of cores. Although the exact architectural details
and trade-offs of such systems are still unclear, it is anticipated that
an overall concurrency level of <span class="math"><math xmlns="http://www.w3.org/1998/Math/MathML"><mrow><mi>O</mi><mo>(</mo><msup><mn>10</mn><mn>9</mn></msup><mo>)</mo></mrow></math></span> threads/tasks will probably be
required to feed all computing units while hiding memory latencies. It
will obviously be a challenge for many applications to scale to that
level, making the underlying system sound like “embarrassingly parallel
hardware.”</p>
        <p>From the programming point of view, it becomes a matter of being able to
expose extreme parallelism within applications to feed the underlying
computing units. However, this increase in the number of cores also
comes with architectural constraints that actual hardware evolution
prefigures: computing units will feature extra-wide SIMD and SIMT units
that will require aggressive code vectorization or “SIMDization”,
systems will become hybrid by mixing traditional CPUs and accelerators
units, possibly on the same chip as the AMD APU solution, the amount of
memory per computing unit is constantly decreasing, new levels of memory
will appear, with explicit or implicit consistency management, etc. As a
result, upcoming extreme-scale system will not only require
unprecedented amount of parallelism to be efficiently exploited, but
they will also require that applications generate adaptive parallelism
capable to map tasks over heterogeneous computing units.</p>
        <p>The current situation is already alarming, since European HPC end-users
are forced to invest in a difficult and time-consuming process of
tuning and optimizing their applications to reach most of current
supercomputers' performance. It will go even worse with
the emergence of new parallel architectures (tightly integrated
accelerators and cores, high vectorization capabilities, etc.) featuring
unprecedented degree of parallelism that only too few experts will be
able to exploit efficiently. As highlighted by the ETP4HPC initiative,
existing programming models and tools won't be able to cope with such a
level of heterogeneity, complexity and number of computing units, which
may prevent many new application opportunities and new science advances
to emerge.</p>
        <p>The same conclusion arises from a non-HPC perspective, for single node
embedded parallel architectures, combining heterogeneous multicores,
such as the ARM big.LITTLE processor and accelerators such as GPUs or
DSPs. The need and difficulty to write programs able to run on various
parallel heterogeneous architectures has led to initiatives such as
HSA, focusing on making it easier to program heterogeneous computing
devices. The growing complexity of hardware is a limiting factor to
the emergence of new usages relying on new technology.
</p>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid3.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid9.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
    </div>
  </body>
</html>
