1 / 13

Status – Week 247

Status – Week 247. Victor Moya. Summary. Streamer. TraceDriver. bGPU Signal Traffic Analyzer. Streamer. Streamer. Use Roger idea of a last use table for the output memory rather than reference counters. How would be the Streamer Pipeline? Stages: Load index data. Add new vertex/index.

daktari
Télécharger la présentation

Status – Week 247

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status – Week 247 Victor Moya

  2. Summary • Streamer. • TraceDriver. • bGPU • Signal Traffic Analyzer.

  3. Streamer

  4. Streamer • Use Roger idea of a last use table for the output memory rather than reference counters. • How would be the Streamer Pipeline? • Stages: • Load index data. • Add new vertex/index. • Search in the output cache. • Add to the vertex FIFO. • Load vertex (n cycles). • Shade vertex (m cycles). • Read vertex from shader (o cycles). • Write vertex to shader (p cycles).

  5. Streamer • Boxes? • 1 one box. • N boxes: • Streamer frontend (load index). • Vertex loader. • Output cache. • Vertex FIFO. • Shader + Output memory. • Signals?

  6. TraceDriver • Very buggy implementation. • Lacks most features. • Needs a lot of more work before a ‘good’ trace can be parsed.

  7. bGPU • Passes the simple OpenGL trace we are currently using (just one triangle). • Works for multiple frames. • Still many untested things and unsolved bugs (for example memory leakage from OptimizeDynamicMemory objects ...). • The simulation model is very simple: only 1 vertex shader.

  8. bGPU • Propose a first simulation model: • 1 vertex shader (later 1 vs 4 ps). • 2 vertex shader (later 2 vs 4 ps). • 4 vertex shader (later 4 vs 8 ps). • ? • Most units need a lot of work before they can be used to produce a good simulation (MemoryController, Shader, Streamer).

  9. Signal Trace Analyzer • Working prototype for the Analyzer GUI.

  10. How to commit code • New files and modified files are not sent zipped using mail to other programmers. • New files and modified files are commited using CVS. • New files and modified files must keep the code style rules: • Indentation is 4 spaces, not 3 spaces, not a tab. • Newlines use the UNIX format not the Windows lf/cr format. • DO NOT COMMIT CODE WITHOUT FOLLOWING THIS RULES.

  11. How to commit code • How to commit code with CVS? • Put the modified/new files in your cvs image directory. • New files and directories are added using ‘cvs add filename’. • BEFORE COMMITING ALWAYS DO AN UPDATE: ‘cvs update’ in the cvs source root directoy. • How to resolve update conflicts? • COMMIT: ‘cvs commit’. • Put some comments with what has changed in the code would be nice. • Send those comments in a commit notice to the other programmers is also nice.

  12. How to commit code • How to resolve update conflicts? • 1) cvs marks in the source the conflict regions and puts the two code versions. • 2) it shouldn’t compile correctly. • 3) if it is code you have modified and the conflict is with the old version -> use your code. • 4) if it is code someone else has modified and committed but you have not touched -> use the original code.

  13. How to commit code • 5) if it is code someone else has modified and committed and you have also modified -> • a) you know what to do -> do you really know? -> really-> really really really? -> do it. • b) you don’t know -> ask. • 6) you don’t know what to do -> ask.

More Related