Changeset 280 for anr/section-3.2.tex
- Timestamp:
- Nov 30, 2010, 6:11:33 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/section-3.2.tex
r277 r280 5 5 either a HPC application (an application running on a PC that must be accelarate), 6 6 or an embedded application (a standalone application), 7 or a sub-system application of a larger design.} 7 or a sub-system application of a larger design. 8 The figure shows that the design flow of embedded and sub-system applications does not differ 9 except in the generation step and that the design flow of HPC application just adds a 10 preliminary step. 11 } 8 12 \begin{figure}[hbtp]\leavevmode\center 9 \includegraphics[width= .8\linewidth]{flow}13 \includegraphics[width=1.0\linewidth]{flow2} 10 14 \caption{\label{coach-flow} COACH design flow} 11 15 \end{figure} … … 24 28 ASIP (the process runs as a software task on a SoC processor enhanced with dedicated instructions), 25 29 and hardware (the process is implemented as a synthesized hardware coprocessor). 30 \begin{SUPPRESSEDENV} 26 31 \item[Application compilation:] 27 \begin{SUPPRESSEDENV}28 32 Once the SoC architecture is validated through performances analysis, 29 33 COACH will generate automatically an executable containing the host application and … … 33 37 loading the bitstream on an FPGA and running the executable on PC. 34 38 \end{SUPPRESSEDENV}\begin{ADDEDENV} 39 \item[Generation:] 35 40 Once the SoC architecture is validated through performances analysis, 36 41 COACH generates its bitstream in the case of HPC or embedded application, … … 60 65 \begin{description} 61 66 \item[\textit{Design Space Exploration by Virtual Prototyping}]: 62 63 64 65 67 The COACH environment will allow to easily map a parallel application (formally described as 68 an abstract network of process and communication channels) 69 COACH will permit the system designer to explore the design space, and to define the best 70 hardware/software partitioning of the application. 66 71 \item[\textit{Integration of system level modeling and HLS tools}]: 67 68 69 70 71 72 73 74 72 COACH will support the automated generation of hardware accelerators when required 73 by using High-Level Synthesis (HLS) tools. These HLS tools will be 74 fully integrated into a complete system-level design environment. 75 Moreover, COACH will support both data and control dominated applications, 76 and the HLS tools of COACH will support a common language and coding style 77 to avoid re-engineering by the designer. 78 COACH will provide a tool which will automatically explore the micro-architectural 79 design space of coprocessor. 75 80 \item[\textit{High-level code transformation}]: 76 77 78 79 80 81 82 83 84 81 COACH will allow to optimize the memory usage, to enhance the parallelism through 82 loop transformations and parallelization. The challenge is to identify the coarse 83 grained parallelism and to generate, 84 from a sequential algorithm, application containing multiple communicating 85 tasks. COACH will adapt techniques which were developed in the 1990 for 86 the construction of distributed programs. However, in the context of HLS, there are 87 several original problems to be solved, related to the FIFO communication channels and with 88 memory optimization. 89 COACH will support code transformation by providing a source to source C2C tool. 85 90 \item[\textit{Unified Hardware/Software communication middleware}]: 86 87 88 89 90 91 COACH will rely on he SoCLib experience to implement an unified hardware/software communication 92 infrastructure and communication APIs (Application Programming Interface), to support 93 communications between software tasks running on embedded processors and dedicated 94 hardware coprocessors. The main issue here is to support easy migration 95 from a software implementation to an hardware implementation. 91 96 \item[\textit{Processor customization}]: 92 93 94 95 96 97 ASIP (Application Specific Instruction Processor) design will be addressed by the COACH project. 98 COACH will allow system designers to explore the various level of interactions between 99 the original CPU micro-architecture and its extension. It will also allow to retarget 100 the compiler instruction-selection pass. Finally, COACH will integrate ASIP synthesis 101 in a complete System-level design framework. 97 102 \end{description} 98 103 … … 103 108 a communication middleware for HPC, 104 109 5 HAS tools (control dominated HLS, data dominated HLS, Coarse grained HLS, 105 Memory optimi sation HLS and ASIP),110 Memory optimization HLS and ASIP), 106 111 3 architectural templates that are synthesizable and that can be prototyped, 107 112 one design space exploration tool, 108 2 operating systems (DNA/OS and MUTEKH).113 1 operating systems (DNA/OS). 109 114 \\ 110 The framework f onctionalitywill be demonstrated with the demonstrators115 The framework functionalities will be demonstrated with the demonstrators 111 116 (see task-7 page~\pageref{task-7}) and the tutorial example (see task-8 112 117 page~\ref{subtask-tutorial}).
Note: See TracChangeset
for help on using the changeset viewer.