3D-DRESD CiTiES

451 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
451
On SlideShare
0
From Embeds
0
Number of Embeds
33
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

3D-DRESD CiTiES

  1. 1. CITiES .:: Project Presentation ::.
  2. 2. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  3. 3. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  4. 4. Point-to-Point <ul><li>Point-to-point interconnections </li></ul><ul><ul><li>Regular/Uniform </li></ul></ul><ul><ul><ul><li>Well-defined interconnection topology (e.g. full connected graph) </li></ul></ul></ul><ul><ul><ul><li>Flexibility and regularity, but area overhead </li></ul></ul></ul><ul><ul><li>Custom </li></ul></ul><ul><ul><ul><li>Ad-hoc interconnection: high-performance and low overhead </li></ul></ul></ul><ul><li>Point-to-point do not scale well, since adding channels requires adding more physical wires </li></ul>4
  5. 5. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  6. 6. Bus (1/3) <ul><li>A bus is a set of spatially adjacent links </li></ul><ul><ul><li>They define a single , shared communication channel ( bus transparency ) </li></ul></ul><ul><li>Access to a bus is concurrent, thus contention resolution is required </li></ul><ul><ul><li>An arbiter manages concurrent access requests and assigns the resource to the user </li></ul></ul><ul><ul><ul><li>Area and computational overhead </li></ul></ul></ul><ul><li>Different kind of bus </li></ul><ul><ul><li>Hierarchical </li></ul></ul><ul><ul><ul><li>e.g. IBM CoreConnect </li></ul></ul></ul><ul><ul><li>Split-bus </li></ul></ul><ul><ul><ul><li>Reduce capacity load </li></ul></ul></ul>5
  7. 7. Bus (2/3) <ul><li>Hierarchical bus </li></ul><ul><ul><li>The logical communication infrastructure is divided into subdomains </li></ul></ul><ul><ul><ul><li>Each domain is independent to the others </li></ul></ul></ul><ul><ul><ul><li>A bridge is used to connect different, independent domains </li></ul></ul></ul>6
  8. 8. Bus (3/3) <ul><li>Split bus </li></ul><ul><ul><li>Reduce capacity load seen from the user interface </li></ul></ul><ul><ul><li>Each segment can be used to address different domains in the system </li></ul></ul>7
  9. 9. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  10. 10. Network-on-Chip (1/4) <ul><li>GENERAL IDEA : borrow theories and applications from the well-known data communication field, e.g. LAN, WAN, MAN... </li></ul><ul><ul><li>On-chip network </li></ul></ul><ul><li>RATIONALE : to achieve high-performance communication we need </li></ul><ul><ul><li>Reliability </li></ul></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><li>Flexibility </li></ul></ul><ul><ul><li>Adaptability </li></ul></ul><ul><ul><li>Repeatability, ease-to-reuse approach </li></ul></ul><ul><ul><ul><li>Regular structures and concepts </li></ul></ul></ul>8
  11. 11. Network-on-Chip (2/4) <ul><li>XPIPES , first true NoC architecture used for multiprocessing elements based SoC </li></ul><ul><ul><li>Highly-parameterizable static NoC with several high-performance issues </li></ul></ul><ul><ul><ul><li>Pipelined inter-router connections </li></ul></ul></ul><ul><ul><ul><li>IN/OUT buffering </li></ul></ul></ul><ul><ul><ul><li>Reliable communication through communication protocols </li></ul></ul></ul><ul><ul><li>It is defined by a library of network element macros (SystemC defined) </li></ul></ul><ul><li>XPIPES COMPILER , reads the library, reads the user inputs and generate a Verilog instantiable NoC architecture </li></ul>9
  12. 12. Network-on-Chip (3/4) <ul><li>Layered approach to design allows </li></ul><ul><ul><li>independent optimization </li></ul></ul><ul><ul><li>Separation of concerns </li></ul></ul><ul><ul><li>Flexibility </li></ul></ul><ul><li>XPIPES is based on the Smart Stack </li></ul><ul><li>Assumptions </li></ul><ul><ul><li>The physical layer has non-zero probability of error </li></ul></ul><ul><ul><ul><li>We have to achieve a threshold of reliability </li></ul></ul></ul><ul><ul><li>Packet-switched network </li></ul></ul><ul><ul><li>End-to-end delivery control based on the use of network elements </li></ul></ul>10
  13. 13. Network-on-Chip (4/4) <ul><li>Smart Stack layered structure ( bottom-up ) </li></ul>11 DATA LINK LAYER NETWORK LAYER TRANSPORT LAYER Increase reliability of the link (ARQ, FEC) End-to-end delivery control Decomposes messages into packets
  14. 14. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  15. 15. General overview <ul><li>The proposed approach consists of: </li></ul><ul><ul><li>a fix part </li></ul></ul><ul><ul><li>a set of reconfigurable slots </li></ul></ul>
  16. 16. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  17. 17. Fix part <ul><li>The fix part consists of: </li></ul><ul><ul><li>a set of computational components </li></ul></ul><ul><ul><li>a set of CI components </li></ul></ul><ul><li>These components cannot be reconfigure at run time, since they have to provide a reliable communication channel between the reconfigurable slots </li></ul>
  18. 18. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  19. 19. Reconfigurable slots <ul><li>Each slot can be filled with: </li></ul><ul><ul><li>a computational module </li></ul></ul><ul><ul><li>a communication module </li></ul></ul><ul><li>Both these two kind of slot share the same interface, since they have to be interchangeable at run time </li></ul>
  20. 20. Computational modules <ul><li>Computational modules do not interfere with the communication infrastructure wires </li></ul><ul><ul><li>This is possible thanks to the Early Access Partial Reconfiguration (EAPR) flow </li></ul></ul><ul><li>Computational module logic can use all the resources that are not occupied by the CI logic </li></ul>
  21. 21. CI modules <ul><li>CI modules can either use the CI wires in order to change their routing or leave them unchanged </li></ul><ul><li>In this way it is possible to dynamically change the CI in order to achieve the desired configuration of communication channels </li></ul>
  22. 22. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  23. 23. A complete example
  24. 24. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  25. 25. Adaptation to point-to-point
  26. 26. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  27. 27. Adaptation to bus
  28. 28. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  29. 29. Adaptation to NoC
  30. 30. Outline <ul><li>Standard Communication Infrastructures (CIs): </li></ul><ul><ul><li>Point-to-point </li></ul></ul><ul><ul><li>Bus </li></ul></ul><ul><ul><li>Network-on-Chip (NoC) </li></ul></ul><ul><li>The proposed approach: </li></ul><ul><ul><li>General overview </li></ul></ul><ul><ul><li>Fix part </li></ul></ul><ul><ul><li>Reconfigurable slots </li></ul></ul><ul><ul><li>A complete example </li></ul></ul><ul><ul><li>Adaptation to point-to-point </li></ul></ul><ul><ul><li>Adaptation to bus </li></ul></ul><ul><ul><li>Adaptation to NoC </li></ul></ul><ul><li>Conclusions and future work </li></ul>
  31. 31. Conclusions and future work <ul><li>The proposed approach is just a draft </li></ul><ul><li>In order to use the proposed ideas, it is necessary to explore: </li></ul><ul><ul><li>the size of the fix part of the architecture </li></ul></ul><ul><ul><li>the size of each reconfigurable slot </li></ul></ul><ul><ul><li>the number of slices occupied for the CI for each reconfigurable slot </li></ul></ul>
  32. 32. The end <ul><li>Thank you for your attention </li></ul><ul><li>Do you have any questions? </li></ul>

×