1 / 126

OCP-IP Governing Steering Committee Meeting Teleconference April 23, 2009

OCP-IP Governing Steering Committee Meeting Teleconference April 23, 2009.

jada
Download Presentation

OCP-IP Governing Steering Committee Meeting Teleconference April 23, 2009

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. OCP-IPGoverning Steering Committee MeetingTeleconferenceApril 23, 2009

  2. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35 AM: Metadata WG Update (Prashant) 5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James)7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  3. Call to Order and Agenda Review (Ian) • Call to Order • Welcome from the President • Review Agenda • Any additional items?

  4. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35AM:Metadata WG Update (Prashant)5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  5. 8:05- 8:10 AM: 2009 Goals 8:10- 8:50 AM: AI Review (Ian) - CoreCreator Shipments - Princeton Sponsor Level Upgrade8:50- 9:00 AM: PR Update (Joe) 9:00- 9:20 AM: Motion to Adjourn/ Break/ Reconvene 9:20- 9:30 AM: Recruiting Update (Joe) 9:30- 9:40 AM: Budget/Cash Flow Update (Ian) 9:40- 9:55 AM: Administrative Update (VTM) 9:55- 10:00 AM: Enabling Resolution 10:00 AM: Motion to Adjourn

  6. Vote to Approve Last GSC Meeting Minutes • 29th GSC Meeting • January 15, 2009 in Milpitas, California

  7. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35 AM: Metadata WG Update (Prashant) 5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  8. Next GSC Meeting (Ian) • 31st GSC Meeting • West Coast? Portland, Oregon? • Should this be telecon only? • We do need occasional face-to-face meetings • Date around week of July 13th?

  9. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35AM:Metadata WG Update (Prashant)5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  10. OCP-IP Meta-Data Working GroupPlans and status OCP GSC meeting Apr 09

  11. 2009 Goals given to MDWG by TVWG/GSC • Spirit interoperability • Implement OCP within existing Spirit format • Spirit enhancements • Propose and drive modifications into IP-XACT standard • Core compatibility reports • Ability to automatically compare OCP interface configurations • Release IP-XACT checkers to OCP-IP community • Enhance for OCP 3.0

  12. People involved • Nokia: Vesa Lahtinen • TI: Prashant Karandikar, Anne-Francoise Joanblanq, Olivier Sagner, Bob Maaraoui, James Aldis • Sonics: Kamil Synek, Pascal Chauvet, Drew Wingard • Synopsys: Mark Noll • STMicroelectronics: Serge Hustin, Christophe Amerijckx • Magillem Design Services: Cyril Spasevski, Stephane Guntz • Toshiba ( Yasuhiko ) • OCP-IP: Ian Mackintosh • Mentor Graphics later? • John Wilson already on the reflector, waiting for a Mentor participant to the teleconferences

  13. Background • OCP-IP has been talking about an IP-XACT description for several years, now we just simply need to provide it (in 2008, originally). Even if it means making some compromises. • Clean and elegant solution that fits all OCP users should be the goal, but it has to be something that complies with IP-XACT 1.4 and we need to get ok from key tool providers so that their tools will be able to use the description. • We should not make a monster. If somebody is only operating on small fixed OCP subsets, the full configurability of OCP should be hidden somehow. Still the description should also support the full set of configuration options. • Eventually IP-XACT description should replace rtl.conf.

  14. Spirit Interoperability Implement OCP within existing spirit format • Use the Magillem/Sonics proposal as basis • ST-style checking is used to validate an IP description Status : • Vendor Extension Schema for Busdef and Abstraction Definition have been defined and available in SVN repository. • OCP configuration Checker is also available in SVN repository. • Both of above deliveries have been conceptually agreed within MDWG and pending final approval. Next Steps • Documentation ( 2Q09 )

  15. Spirit Enhancement Propose and drive modifications into IP-XACT standard • Proposal for configurable bus interfaces was not accepted for IP-XACT1.5 • Spirit Consortium SWG agreed to put staging process for configurable bus interface solution , it may become part of the schema sometime later.

  16. Core Compatibility report Ability to automatically compare OCP interface configurations • Check the inter-interface consistency (Current configuration compliance checks) • Check consistency of a connected master / slave interface pair (Current interface interoperability checks) • Check consistency of the ports and parameters • Generate the rtl.conf file out of configured IP-XACT parameter list (legacy support) • Configure IP-XACT parameter list based on an rtl.conf file and give rtl.conf files of OCP standard profiles as examples (legacy support) • This activity is expected to happen during Q2/Q3 09

  17. OCP3.0 Add OCP 3.0 signals and parameters to bus definition schema • Activity duration is TBD

  18. Release IP-XACT checker to OCP-IP community • Steps for IP-XACT checker release • ocp vendor extension schema & checker approval by MDWG members. • Documentation of the schema & checker has been approved by MDWG members

  19. GSC Request to MDWG • Please put proposed schedule for all actions and plans listed • Specifically including goals to MDWG from TWVG/GSC

  20. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35 AM: Metadata WG Update (Prashant) 5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  21. SLD WG Update Mark Burton (GreenSocs), April 2009

  22. Overview • Overview Status for SLD • Goals from TVWG • Mid-term outlook

  23. Summary • Release of TL1, TL2, TL3/4 for OCP in TLM 2.0 • Great Achievement; quality of architecture and code is very high • release was later than planned because of impossibility to schedule volunteer resource (architecture and review as well as code implementation) • number of known gaps in the release • quality control, benchmarking and regression testing can be extended • Outsource project to Greensocs highly successful • project is now finished • GS continuing to manage the SLD WG and provide support and small-scale upgrade effort • SLD WG is still limited to Sonics, TI and Greensocs • Nokia and Cadence have expressed interest in reviewing the kit • Still talking to other companies about joining the WG • SLD WG plans are to • Do incremental work on the current code • Nothing else

  24. SLD WG Status

  25. OCP-3 TLM/SLD Standards • Cache coherency extensions to OCP • This is on our roadmap for 2009 • No committed resource • Therefore impossible to predict delivery date

  26. The SLD Mid-Term Vision - unchanged • Ensure that OCP users have a 'complete' modelling infrastructure available • multiple levels of abstraction (pure-functional to cycle-accurate) and use models (software development, architecture exploration, etc) • completeness means • bus interface , performance monitoring interface ,system debug interface and configuration interface • Make this modelling infrastructure standards compliant. • E.g. drive existing OCP-IP experience and expertise into OSCI-TLM • Maintain alignment between OSCI-TLM OCP-IP

  27. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35 AM: Metadata WG Update (Prashant) 5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  28. Network-on-Chip benchmarking workgroup, status update April 2009, Erno Salminen

  29. Current status • Erno Salminen is currently acting as a chairmain • Application modeling article • Short version published at Embedded.com • Camera ready version sent to IET Computer and Digital Techniques in April • Slide presentation will be published during DATE • Simulation tool Transaction Generator will become open source (more info a bit later)

  30. Current status (2) • Video decoding benchmark • Specification document being accepted by the workgroup • Vote 15th of April • Ready for member/GSC review (as/required?) • Describes the traffic patterns in HDTV decoding application • Multiprocessing chip, shared memory communication via external DRAM • Few accelerators in addition to CPUs • Bandwidth, burst size, target distribution • Prepared by Krishnan Srinivasan, Sonics Inc. • This document will be formatted as a white paper

  31. Current status (3) • Call for benchmarks has not succeeded yet • Teleconference held with EEMBC consortium (Markus Levy, Shay Gal-on) • We discussed collaboration between NoC wokrgroup and EEMBC • They showed moderate interest but saw no immediate benefits for themselves • Our workgroup aims to create traffic profiles from EEMBC’s benchmark programs, especially from Multibench • System-level design workgroup also contacted (Mark Burton) but no concrete advances yet

  32. Transaction Generator (TG) • Executes the NoC benchmarks • Reads the XML workload description • Injects/ejects data to/from network • Checks integrity, collects statistics • Implemented in SystemC • Originally developed at Tampere University of Technology • Will be published as open source in Q2-Q3 of 2009 • Promotes the availability of benchmarks

  33. TG (2) • Application • Kahn process network • Separation of computation and communication 28 A B 20 4 F C 25 8 30 D E • Application model and XML format were derived from the work done with TG • Only internal usage so far • Some effort needed in documentation • Mapping • Defines where tasks are executed I II III IV V Transaction Generator • Computation Architecture • Highly abstracted including characteristic parameters PE1 PE2 PE3 PE4 • Communication Architecture • Network model is cycle-accurate or event-accurate with time estimation Network model Legend: Inter-task transfer Mapping/grouping Initialization event Task Group Processing element (PE)

  34. Transaction Generator (3) • The license will be LGPL • GNU Lesser General Public license • Published changes will be LGPL, can be combined to proprietary SW if unmodified • Open questions • Where the repository will reside? • Detailed schedule • Documentation • Example designs

  35. Ongoing activities • Message-passing video encoder • Multiprocessor system implemented in FPGA • Runs MPEG-4 encoder • Initial measurements have been carried out • Detailed profiling is ongoing • Complements the shared mem. video benchmark • Medical image processing • No access to realistic input data sets (medical images of patients) • We will investigate if realistic traffic profiles can be obtained with synthetic images

  36. Ongoing activities • Guideline preparation • Will start in full force once the TG has been published • How to do measurements (higher priority) • How to create traffic models • Promotion plan is still being prepared • Finding more benchmarks • Easier said than done

  37. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35 AM: Metadata WG Update (Prashant) 5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  38. Break

  39. 5:00- 5:10 AM: Call to Order, Introductions, Agenda Review, Last Minutes (Ian)5:10- 5:15 AM: Next GSC Meeting (Ian) 5:15- 5:35 AM: Metadata WG Update (Prashant) 5:35- 6:05 AM: System Level Design WG Update (Mark/James)6:05- 6:25 AM: NoC BWG Update (Erno) 6:25- 6:45 AM: Motion to Adjourn/ Break/ Reconvene 6:45- 7:15 AM: Specification WG Status (Drew) - Brief OCP v3.0 Update (Drew) - OCP v4.0 (Drew) - TI C2C Proposal (James) 7:15- 7:25 AM: FVWG Discussion (Ian) 7:25- 7:45 AM: Debug WG Update (Bob) 7:45- 7:50 AM: Technical Vision WG Status / Restated (Ian) 7:50- 8:05 AM: Progress in Asia (Ian)

  40. Specification WG 2009 Plan

  41. Specification WG Status • 3.0 Member Review draft • Essentially complete – expect by next week • 3.0 Specification bubble items • Relaxation of tag ordering rules • Agreed • Extension to profile 1 (add optional MRespAccept) • Retracted

  42. Next Specification Releases • OCP 3.0 (Member Review: May 09) • Focus is cache coherence extensions (major) • Verification guidelines delayed until later release • Also • Power management signaling (disconnect) • Write response extension • Profile 3

  43. Specification WG Issues • Cache coherence extensions • Planning to enable non-member reviewers (under NDA) • No motivation to cover in CoreCreator • Little clear drive for work beyond 3.0

  44. CoreCreator 4.0 (The old version) Status Check • Need to EOL this year • Only covers OCP 1.x and 2.0 • Getting very old (support more difficult) • Suggestion: • No new keys after July ’09 (~ 1 year after CC 2) • All keys expired by July ’10 • Can we go faster?

  45. OCP 4.0 Concept • See Ian’s slides

  46. OCP SPEC ROADMAP Existing OCP v 3.0 Planned ADDITION OCP v 4.0 Message Style Network Style Dedicated Wires (Cmd, Add, Data & Response, Control, etc.) Fewer Wires (Control + Payload) Bus-like (parallelism) Packet-style 46

  47. IMPORTANCE 47

  48. OCP 4.0 Status • Ian out prospecting • Drew needs to engage as well • Ian’s OCP 4.0 status • … • Suggest we plan 4Q’09 start

  49. OCP-IP Standardisation RoadmapLow Latency Chip-to-Chip Memory-Mapped Interface April 2009 James Aldis, Texas Instruments

  50. Summary • TI wants to standardise a memory-mapped chip-to-chip protocol • high bandwidth, low latency • lower latency than eg PCI-Express or Unipro • tightly-coupled with on-chip memory-mapped bus protocols • moderate pin count (eg 20 to 100 pins) • one key goal: • sharing of system memory, including CPU cache operations • TI wants OCP-IP to consider hosting this standardisation • strong correlation with the possible “OCP network socket” • agreement of semantics and ordering rules on- and off-chip • likely need for rich configurability • known to be quick and efficient workplace • Would apply only to the “protocol” and not to the physical interface • voltage, clocking, drive strength, pin locations, etc all outside OCP-IP scope • TI is looking at a number of options; OCP-IP is one of them • Need OCP-IP GSC feedback on the ideas in these slides • All information in these slides is preliminary and speculative

More Related