Changeset 237 for anr/section-3.1.tex


Ignore:
Timestamp:
Feb 16, 2010, 5:24:12 PM (14 years ago)
Author:
coach
Message:

Paul coquilles

File:
1 edited

Legend:

Unmodified
Added
Removed
  • anr/section-3.1.tex

    r235 r237  
    88\subsubsection{High Performance Computing}
    99% Un marché bouffé par les archi GPGPU tel que le FERMI de NvidiaCUDA programming language
    10 High-Performance Computing (HPC) world is composed of three main families of architectures:
     10The High-Performance Computing (HPC) world is composed of three main families of architectures:
    1111many-core, GPGPU (General Purpose computation on Graphics Unit Processing) and FPGA.
    12 The two first families are dominating the market by taking benefit
     12The first  two families are dominating the market by taking benefit
    1313of the strength and influence of mass-market leaders (Intel, Nvidia).
    1414%such as Intel for many-core CPU and Nvidia for GPGPU.
     
    5151\subsubsection{System Synthesis}
    5252Today, several solutions for system design are proposed and commercialized.
    53 The existing commercial or free tools does not
     53The existing commercial or free tools do not
    5454cover the whole system synthesis process in a full automatic way. Moreover,
    5555they are bound to a particular device family and to IPs library.
     
    8484set of constraints (area, power, frequency, ...) to a micro-architecture at
    8585Register Transfer Level (RTL).
    86 Several academic and commercial tools are today available. Most common
     86Several academic and commercial tools are today available. The most common
    8787tools are SPARK~\cite{spark04}, GAUT~\cite{gaut08}, UGH~\cite{ugh08} in the
    8888academic world and CATAPULTC~\cite{catapult-c}, PICO~\cite{pico} and
    89 CYNTHETIZER~\cite{cynthetizer} in commercial world.  Despite their
     89CYNTHETIZER~\cite{cynthetizer} in the commercial world.  Despite their
    9090maturity, their usage is restrained by \cite{IEEEDT} \cite{CATRENE} \cite{HLSBOOK}:
    9191\begin{itemize}
     
    9898designs are multi-constrained,
    9999Moreover, low power consumption constraint is mandatory for embedded systems.
    100 However, it is not yet well handled or not handle at all by the synthesis tools already available,
     100However, it is not yet well handled or not handled at all by the synthesis tools already available,
    101101\item The parallelism is extracted from initial algorithmic specification.
    102102To get more parallelism or to reduce the amount of required memory in the SoC, the user
     
    106106pipelining, current HLS tools do not provide support for design space exploration neither
    107107through automatic loop transformations nor through memory mapping,
    108 \item Despite they have the same input language (C/C++), they are sensitive to the style in
    109 which the algorithm is written. Consequently, engineering work is required to swap from
     108\item Despite having the same input language (C/C++), they are sensitive to the style in
     109which the algorithm dis written. Consequently, engineering work is required to swap from
    110110a tool to another,
    111111\item They do not respect accurately the frequency constraint when they target an FPGA device.
    112112Their error is about 10 percent. This is annoying when the generated component is integrated
    113 in a SoC since it will slow down the hole system.
     113in a SoC since it will slow down the whole system.
    114114\end{itemize}
    115115Regarding these limitations, it is necessary to create a new tool generation reducing the gap
Note: See TracChangeset for help on using the changeset viewer.