DOCSLIB.ORG

Khronos Overview Dec14

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Khronos Overview December 2014 Neil Trevett Khronos President NVIDIA Vice President Mobile Ecosystem @neilt3d © Copyright Khronos Group 2014 - Page 1 Why Do We Need Standards? • Standards are interoperability interfaces - They enable communities to communicate and independently innovate • Compelling user experiences can be created inexpensively to build mass markets - Don’t slow growth with functionality fragmentation that adds no value • E.g. Wireless and IO standards - GSM/EDGE, UMTS/HSPA, LTE, IEEE 802.11, Bluetooth, USB … Standards drive mobile market growth by expanding device capabilities © Copyright Khronos Group 2014 - Page 2 Khronos Connects Software to Silicon • Open Consortium creating OPEN STANDARD APIs for hardware acceleration - Any company is welcome – many international members • Defining the low-level silicon interfaces needed on every platform - Graphics, compute, rich media, vision, sensor and camera processing • Commitment to ROYALTY-FREE specifications for use by the whole industry - State-of-the art IP framework to protect members AND the standards • Non-profit organization - Membership fees cover operating and engineering expenses • Create and publish API Specifications AND Conformance Tests - For cross-vendor portability • Strong industry momentum - 100s of man years invested by industry experts Silicon Well over a BILLION people use Khronos APIs Every Day… Software © Copyright Khronos Group 2014 - Page 3 BOARD OF PROMOTERS Over 100 members worldwide Any company or university welcome to join © Copyright Khronos Group 2014 - Page 4 http://accelerateyourworld.org/ © Copyright Khronos Group 2014 - Page 5 Standards in the Real World Right time to Standardize? Vendor differences adding no value - Darwinian industry is still fragmentation is slowing growth – clear experimenting with what works goals emerge for a standard and what doesn’t REFINE BY COMMITTEE DESIGN BY COMMITTEE Industry agrees on what to standardize Experimentation and design by – cooperative refinement from multiple committee can be viewpoints creates a robust solution slow and unfocused A good standard enables A bad standard stifles innovation implementation innovation and causes commoditization Proven processes to accelerate time to a productive ecosystem Proven IP Framework that protects Members IP and specifications in the market A forum for the industry to come together to enable efficient silicon innovation © Copyright Khronos Group 2014 - Page 6 The Value of Khronos Participation See an early window Have a voice in Develop into the future of the how key products in Products are aligned industry technology standards parallel with with global market roadmap before evolve to suit spec drafting needs and trends products are your business for faster time developed needs to market Members can ship products faster than non-members Gather Industry Draft Specifications Publicly Release Non-members Requirements for future Confidential to Specifications and Release silicon acceleration Khronos members Conformance Tests Products The Khronos standardization process is proven to RAPIDLY generate industry consensus on future hardware acceleration functionality to EFFICIENTLY create new market opportunities © Copyright Khronos Group 2014 - Page 7 IP Policy, Adoption & Conformance, and Working Group Processes Note: These slides are for informational purposes only. Please consult the Khronos Membership Agreement, the Khronos Adopters Agreement and the Khronos Trademark Guidelines for the exact legally binding language. © Copyright Khronos Group 2014 - Page 8 Specification Development Phases Scope of Work proposals Design Proposals accepted No more core accepted from any member from any member specification changes Previous version Gather Discussion and voting on Specification Specification of specification Requirements requirements Development Ratification Spec public release after Ratification vote Decision to develop Scope of Work for new Ratification vote in by the Board of new release spec version agreed Working Group Promoters Proposals for Extensions to any version of a Specification can be made and approved at any time - Vendor Extension – no approval needed – but Khronos still designates registry key - Multi-Vendor Extension – no approval needed – but Khronos still designates registry key - Khronos Extension – Working group approval needed – specification Ratified and IP license applies © Copyright Khronos Group 2014 - Page 9 Working Group Decision Process Companies in good standing can vote Attendance at two of the last three working group meetings Each company gets one vote Regardless of membership level, company size or number of representatives at meeting Companies can vote either through attendance or by email Yay, nay, or abstain Any member can make Most votes pass with 66% of non-abstaining votes design proposals Ratification votes requires 3/4 majority Proposal The discussion can take place on Proposal Iterative process both email list and on calls Proposal Working Group Chair ensures all proposals are put on agenda Email list / 100% No Documents Working Group Discussion Consensus? Vote? repository All proposals are available Yes to all working group Yes The proposal needs members to review as No soon as they are posted 66% of the non- abstaining vote to be accepted Approved Declined The proposal is Discussion can be accepted by the reopened by working working group group vote © Copyright Khronos Group 2014 - Page 10 Ratification Process The board reviews the specification package for completeness: • 2 independent implementations Working group chair sends redline and Members review specification (1 for extensions) clean release candidate to Promoters for IP inclusion. Members may • Conformance tests and Adoption program and all members. This starts the file exclusion certificates to • Logo and trademark ratification clock. No further functional exclude essential IP during • Khronos Processes have been followed changes to the specification this period Each board member has one vote IP exclusion Each company certificates can no has one vote longer be filed. Working Group Board SpecificationSpecification Working Group Ratification vote Ratification period (42 days) ratification Specification Released DevelopmentDevelopment Ratification vote passes vote Unapproved specifications are sent back to working group Specification is Ratified and approved for release. The mutual IP license is triggered © Copyright Khronos Group 2014 - Page 11 Khronos IP Framework - Balanced Protection Khronos Members agree not to assert IP claims against other Members or Adopters for CONFORMANT IMPLEMENTATIONS OF RATIFIED Specifications No Implementation IP is licensed – Member can exclude JUST IP explicitly in the specification participation in specific Working Groups Disclosed IP – named patent claims can be excluded from the mutual license IP Licensed License ONLY applies to conformant Only implementations of ESSENTIAL IP is licensed Khronos specifications (no commercial alternatives ) IP typically licensed is very narrow BUT is the IP needed to protect the specification for use in the industry © Copyright Khronos Group 2014 - Page 12 Khronos Conformance Process • Implementers of Khronos specifications must be Adopters and pass conformance - Else NOT covered by the Khronos IP framework and cannot use the trademark! • Khronos administers an Adopters Program for each API - Adopters program provides full test access and trademark license for small fee Company Company executes Port and Upload passing test Successful Review of results implementing Adopters Agreement execute tests results to Khronos enables products to use Khronos Khronos spec and pays fee on products to private web-site. trademarks and to be listed on wishes to use the (for unlimited generate test Peer Review by Khronos website trademark products using that results members/Adopters Example: “We spec version) implemented OpenGL ES” Full use of logo Restricted use and trademark trademark (not logo) with small Full use of logo Adopter Benefit with disclaimer disclaimer and trademark language OpenGL ES ™ © Copyright Khronos Group 2014 - Page 13 Adoption Fees You can adopt any specification version. Adopting later versions Some APIs offer discounts includes all earlier versions. if you have adopted One adoption fee lets you earlier versions submit as many products as you wish for that versions of the specification Members get a discount on adoption! © Copyright Khronos Group 2014 - Page 14 Conformance Reporting and Verification Your customers can verify on the Khronos website that your product passed conformance and you are eligible to use the logo and are covered by the mutual IP license grant Note the multiple conformance submissions for OpenGL ES by one company – one per range of similar products Khronos has very precise rules for what range of products can be regarded as similar and so covered by one submission. Rules are defined in the Conformance Process Document © Copyright Khronos Group 2014 - Page 15 Adoption through the Industry Food Chain Each company implementing and promoting a product must be an IP Block Included in SOC Included in Device Adopter and pass conformance to use logo and participate in mutual IP license Example 1: = 3 Adopters Company A Company B Company C 3 test submissions Example 2: = 1 Adoption fee, Company A Company A Company A 1 test submission Company A is not selling IP or SOC as a For efficiency, Companies A, B and C in example can refer to separate product – so
Recommended publications
  • GLSL 4.50 Spec

    GLSL 4.50 Spec

    The OpenGL® Shading Language Language Version: 4.50 Document Revision: 7 09-May-2017 Editor: John Kessenich, Google Version 1.1 Authors: John Kessenich, Dave Baldwin, Randi Rost Copyright (c) 2008-2017 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast, or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be reformatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group website should be included whenever possible with specification distributions.
  • Design Statement Interior Design

    Design Statement Interior Design

    Design Statement Interior Design Sam recrystallizes his salvo singeing heartily, but sharp-tongued Gomer never effaced so betweentimes. Innumerous Chariot frill or blast-off some taenia anarchically, however julienne Traver trichinised logarithmically or settled. Igor still savors compactedly while acerous Walter craning that sheik. Its fluid and sophisticated look at the best consultant will provide the interior is so one is brought to interior design innovation, but together the stress on. Norman is adept at composing convincing personal essays in medicine, written in nursing. As air Of Houston's Top Interior Design Firms We anticipate Full Service making-key Interior Design. Its best statement interior design statements was employed for your document to? You statements designed spaces inspire. Thus, his overall dark neutral color palette will be livened up big bright with rich accents, such sound deep reds and burnt oranges. Why Is A Needs Statement Important? Statement Ceilings are Romantic and Dramatic interior design. This rule goes with accessories, too. The proposed solution and scope and goals of the solution are made clear through this statement. Interior Design Artist Statement Ms Lawson's Foundations 1. What you statements interior is basically puts your statement! Without it, you would face major obstacles and may never see the light of day. Management tool to designing which continue to know what is designed with statements showcase your post the designers. The Houzz Community recommends this professional. Download it to create stunning partitions in small room like i could this user needs and organizational skills you can be something that. Why ello Lob Jakora! We have many different types of subcontractors that we work with on a regular basis and can highly recommend.
  • Implementing FPGA Design with the Opencl Standard

    Implementing FPGA Design with the Opencl Standard

    Implementing FPGA Design with the OpenCL Standard WP-01173-3.0 White Paper Utilizing the Khronos Group’s OpenCL™ standard on an FPGA may offer significantly higher performance and at much lower power than is available today from hardware architectures such as CPUs, graphics processing units (GPUs), and digital signal processing (DSP) units. In addition, an FPGA-based heterogeneous system (CPU + FPGA) using the OpenCL standard has a significant time-to-market advantage compared to traditional FPGA development using lower level hardware description languages (HDLs) such as Verilog or VHDL. 1 OpenCL and the OpenCL logo are trademarks of Apple Inc. used by permission by Khronos. Introduction The initial era of programmable technologies contained two different extremes of programmability. As illustrated in Figure 1, one extreme was represented by single core CPU and digital signal processing (DSP) units. These devices were programmable using software consisting of a list of instructions to be executed. These instructions were created in a manner that was conceptually sequential to the programmer, although an advanced processor could reorder instructions to extract instruction-level parallelism from these sequential programs at run time. In contrast, the other extreme of programmable technology was represented by the FPGA. These devices are programmed by creating configurable hardware circuits, which execute completely in parallel. A designer using an FPGA is essentially creating a massively- fine-grained parallel application. For many years, these extremes coexisted with each type of programmability being applied to different application domains. However, recent trends in technology scaling have favored technologies that are both programmable and parallel. Figure 1.
  • Khronos Template 2015

    Khronos Template 2015

    Ecosystem Overview Neil Trevett | Khronos President NVIDIA Vice President Developer Ecosystem [email protected] | @neilt3d © Copyright Khronos Group 2016 - Page 1 Khronos Mission Software Silicon Khronos is an Industry Consortium of over 100 companies creating royalty-free, open standard APIs to enable software to access hardware acceleration for graphics, parallel compute and vision © Copyright Khronos Group 2016 - Page 2 http://accelerateyourworld.org/ © Copyright Khronos Group 2016 - Page 3 Vision Pipeline Challenges and Opportunities Growing Camera Diversity Diverse Vision Processors Sensor Proliferation 22 Flexible sensor and camera Use efficient acceleration to Combine vision output control to GENERATE PROCESS with other sensor data an image stream the image stream on device © Copyright Khronos Group 2016 - Page 4 OpenVX – Low Power Vision Acceleration • Higher level abstraction API - Targeted at real-time mobile and embedded platforms • Performance portability across diverse architectures - Multi-core CPUs, GPUs, DSPs and DSP arrays, ISPs, Dedicated hardware… • Extends portable vision acceleration to very low power domains - Doesn’t require high-power CPU/GPU Complex - Lower precision requirements than OpenCL - Low-power host can setup and manage frame-rate graph Vision Engine Middleware Application X100 Dedicated Vision Processing Hardware Efficiency Vision DSPs X10 GPU Compute Accelerator Multi-core Accelerator Power Efficiency Power X1 CPU Accelerator Computation Flexibility © Copyright Khronos Group 2016 - Page 5 OpenVX Graphs
  • An Interdisciplinary Approach

    An Interdisciplinary Approach

    Education of Interaction Design – an Interdisciplinary Approach Anirudha Joshi Industrial Design Centre, Indian Institute of Technology, Mumbai, India Anirudha Joshi is a faculty member at the Industrial Design Centre, IIT Mumbai. He teaches and does research in the field of Human-Computer Interaction (HCI) design. His area of research interest is interaction design for needs of developing countries like India. He also works in the area overlapping between software engineering and HCI. He has authored papers related to HCI and given talks in Indian and international conferences and journals. Anirudha conducts workshops on HCI for IT professionals and is also a consultant to several IT companies on HCI projects. Recently, he was the co-chair of the program committee of the first India HCI conference held in December, 2004 in Bangalore. Before joining IIT Mumbai, Anirudha worked in the field of interaction design for software, multimedia and the Internet. Anirudha has a BTech in Electrical Engineering from IIT Mumbai, and a Masters in Design in Visual Communication also from IIT Mumbai. Email: [email protected] The field of interaction design is multidisciplinary in nature. A professional interaction designer needs to take the central responsibility towards all creative aspects of an interactive product. This alone can ensure that well- designed interactive products will emerge with conceptual integrity that proceeds from the thinking of one mind. Education of interaction design therefore needs to be multidisciplinary. The Industrial Design Centre (IDC) in IIT Bombay has had an interdisciplinary approach towards design education for several years. The results of this approach have been very effective for the field of interaction design.
  • Khronos Native Platform Graphics Interface (EGL Version 1.4 - April 6, 2011)

    Khronos Native Platform Graphics Interface (EGL Version 1.4 - April 6, 2011)

    Khronos Native Platform Graphics Interface (EGL Version 1.4 - April 6, 2011) Editor: Jon Leech 2 Copyright (c) 2002-2011 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, repub- lished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specification for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be re- formatted AS LONG AS the contents of the specification are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group web-site should be included whenever possible with specification distributions. Khronos Group makes no, and expressly disclaims any, representations or war- ranties, express or implied, regarding this specification, including, without limita- tion, any implied warranties of merchantability or fitness for a particular purpose or non-infringement of any intellectual property.
  • The Openvx™ Specification

    The Openvx™ Specification

    The OpenVX™ Specification Version 1.0.1 Document Revision: r31169 Generated on Wed May 13 2015 08:41:43 Khronos Vision Working Group Editor: Susheel Gautam Editor: Erik Rainey Copyright ©2014 The Khronos Group Inc. i Copyright ©2014 The Khronos Group Inc. All Rights Reserved. This specification is protected by copyright laws and contains material proprietary to the Khronos Group, Inc. It or any components may not be reproduced, republished, distributed, transmitted, displayed, broadcast or otherwise exploited in any manner without the express prior written permission of Khronos Group. You may use this specifica- tion for implementing the functionality therein, without altering or removing any trademark, copyright or other notice from the specification, but the receipt or possession of this specification does not convey any rights to reproduce, disclose, or distribute its contents, or to manufacture, use, or sell anything that it may describe, in whole or in part. Khronos Group grants express permission to any current Promoter, Contributor or Adopter member of Khronos to copy and redistribute UNMODIFIED versions of this specification in any fashion, provided that NO CHARGE is made for the specification and the latest available update of the specification for any version of the API is used whenever possible. Such distributed specification may be re-formatted AS LONG AS the contents of the specifi- cation are not changed in any way. The specification may be incorporated into a product that is sold as long as such product includes significant independent work developed by the seller. A link to the current version of this specification on the Khronos Group web-site should be included whenever possible with specification distributions.
  • MINUTES Board of Architecture and Interior Design the Breakers One South Court Road Palm Beach, Florida 33480 561.655.6611 July

    MINUTES Board of Architecture and Interior Design the Breakers One South Court Road Palm Beach, Florida 33480 561.655.6611 July

    MINUTES Board of Architecture and Interior Design The Breakers One South Court Road Palm Beach, Florida 33480 561.655.6611 July 28, 2008 9:00 a.m. General Business Meeting Call to Order Mr. Kuritzky, Chair called the meeting to order at 9:05 a.m. Board Members Present: John Ehrig E. Wendell Hall Rossana Dolan Lourdes Solera Eric Kuritzky, Chair Mary Jane Grigsby Roymi Membiela Wanda Gozdz Joyce Shore Board Member Absent: Garrick Gustafson, unexcused Others Present: Mary Ellen Clark, Board Counsel David Minacci, Prosecuting Attorney Juanita Chastain, Executive Director Terri Estes, Government Analyst Trent Manausa Emory Johnson Dwight Chastain Bob Lamar David DeHaas Mickey Marrero Ingrid Burgos Willie Peterson Steven Mickley Board of Architecture and Interior Design July 28-29, 2008 General Business Page 1 of 27 Court Reporter: Alexandra Ramirez, Official Reporting Services, LLC, 524 S. Andrews Avenue, Suite 302N, Ft. Lauderdale, FL 33301 Disciplinary Cases Mr. Minacci requested that the board approve the following cases on a consent agenda. Settlement Stipulation Licensed DBPR vs. Oscar Benetiz Case Numbers 2006-066090 and 2007-013072 PCP: Rodriguez, Wirtz and Gustafson DBPR vs. Hugo De Ley and J Design Group, Inc. Case Numbers 2007-062663 and 2007-049107 PCP: Rodriguez, Wirtz, and Gustafson DBPR vs. William Edwin Wallace Case Number 2007-065241 PCP: Rodriguez, Wirtz, and Gustafson Unlicensed DBPR vs. Teena M. Benton and Benton Drafting and Design Case Number 2007-008550 PCP: Rodriguez, Wirtz, and Gustafson Motion: Ms. Membiela moved that the board approve the settlement stipulations as presented. Second: Mr. Hall seconded the motion and it passed unanimously.
  • Op E N So U R C E Yea R B O O K 2 0

    Op E N So U R C E Yea R B O O K 2 0

    OPEN SOURCE YEARBOOK 2016 ..... ........ .... ... .. .... .. .. ... .. OPENSOURCE.COM Opensource.com publishes stories about creating, adopting, and sharing open source solutions. Visit Opensource.com to learn more about how the open source way is improving technologies, education, business, government, health, law, entertainment, humanitarian efforts, and more. Submit a story idea: https://opensource.com/story Email us: [email protected] Chat with us in Freenode IRC: #opensource.com . OPEN SOURCE YEARBOOK 2016 . OPENSOURCE.COM 3 ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ OPENSOURCE.COM...... ........ .. .. .. ... .... ........ WRITE FOR US ..... .. .. .. ... .... 7 big reasons to contribute to Opensource.com: Career benefits: “I probably would not have gotten my most recent job if it had not been for my articles on 1 Opensource.com.” Raise awareness: “The platform and publicity that is available through Opensource.com is extremely 2 valuable.” Grow your network: “I met a lot of interesting people after that, boosted my blog stats immediately, and 3 even got some business offers!” Contribute back to open source communities: “Writing for Opensource.com has allowed me to give 4 back to a community of users and developers from whom I have truly benefited for many years.” Receive free, professional editing services: “The team helps me, through feedback, on improving my 5 writing skills.” We’re loveable: “I love the Opensource.com team. I have known some of them for years and they are 6 good people.” 7 Writing for us is easy: “I couldn't have been more pleased with my writing experience.” Email us to learn more or to share your feedback about writing for us: https://opensource.com/story Visit our Participate page to more about joining in the Opensource.com community: https://opensource.com/participate Find our editorial team, moderators, authors, and readers on Freenode IRC at #opensource.com: https://opensource.com/irc .
  • Mapping the Range of User Roles in Open Development Games Projects

    Mapping the Range of User Roles in Open Development Games Projects

    Not just users: Mapping the range of user roles in open development games projects Luke Thominet Florida International University Miami, FL, USA [email protected] ABSTRACT love what you’re doing, and they’re not playing a lot, Open video game development systems provide a useful model but they might be writing fanfction, they might be for designing an engaging user experience (UX) research project. drawing, they might be doing other things, and they’re While UX research has typically framed people simultaneously as not actually just a hardcore player. [19] research subjects and users of a technology, some work has also At the 2015 Game Developers Conference, a panel of experienced problematized each of these categorizations. For instance, UX prac- developers discussed their experiences with open development titioners have questioned the framing of people as generic users, projects. In the quote above, Jamie Cheng described how partici- and participatory design has repositioned participants as co-owners pants in these projects were doing a lot more than just playing the of the results of research. This article ofers a complimentary per- game. This paper expands on this observation to review the broad spective by applying the concept of user roles to the activity of range of roles that user-participants adopt in open development participation in open development. Open development, which is the systems. prolonged process where incomplete games are publicly released Broadly speaking, open development is publicly distributing an and iterated on based on player feedback, is fundamentally a UX incomplete game, sharing information about the game develop- research process.
  • Wen-Mei William Hwu

    Wen-Mei William Hwu

    Wen-mei William Hwu PERSONAL INFORMATION Office: Home: Coordinated Science Laboratory 2709 Bayhill Drive 1308 West Main Street, Champaign, Illinois, 61822-7988 Urbana, Illinois, 61801-2307 (217) 359-8984 (217) 244-8270 (217) 333-5579 (FAX) Email: [email protected] EDUCATION Ph.D., Computer Science,1987, University of California, Berkeley B.S., Electrical Engineering, 1983, National Taiwan University, Taiwan CURRENT POSITION Professor and Sanders III Advanced Micro Devices, Inc., Endowed Chair, Electrical and Computer Engineering; Research Professor of Coordinated Science Laboratory, University of Illinois, Urbana-Champaign (UIUC). Chief Technology Officer and Co-Founder, MulticoreWare, Sunnnyvale, California, St. Louis, Missouri, Champaign, Illinois, Chennai, India, Chang-Chun and Beijing, China. Chief Scientist, Parallel Computing Institute, University of Illinois at Urbana-Champaign Board Member, Personify, Inc., Champaign, IL PROFESSIONAL EXPERIENCE September 2016 to present Co-Director (with Jinjun Xiong of IBM) of the IBM-Illinois Center for Cognitive Computing Systems Research, funded by IBM at a total of $8M for five years. The center funds a total of 30+ researchers working on hardware, software, and algorithms for building cognitive computing systems for innovative AI applications. June 2010 to present Co-Director (with Mateo Valero) of the PUMPS Summer School in Barcelona jointly offered by UIUC and the Universitat Politècnica de Catalunya. The summer school has been attended by about 100 faculty and graduate students worldwide every year to study the advanced parallel algorithm techniques for manycore computing systems. June 2008 to present Principle Investigator of the UIUC CUDA Center of Excellence, funded by NVIDIA at over $2.0 M in cash and equipment.
  • Opencl BOF Aug14

    Opencl BOF Aug14

    Neil Trevett Vice President Mobile Ecosystem at NVIDIA President of Khronos and Chair of the OpenCL Working Group SIGGRAPH, Vancouver 2014 © Copyright Khronos Group 2014 - Page 1 Speakers Neil Trevett OpenCL Chair, VP NVIDIA NVIDIA Introduction to Khronos and OpenCL Ecosystem Ralph Potter Research Engineer Codeplay SPIR Luke Iwanski Games Technology Programmer Codeplay SYCL Laszlo Kishonti CEO Kishonti Compute Benchmarking Neil Trevett OpenCL Chair, VP NVIDIA NVIDIA Wrap-up and Questions © Copyright Khronos Group 2014 - Page 2 OpenCL – Portable Heterogeneous Computing • Portable Heterogeneous programming of diverse compute resources - Targeting supercomputers -> embedded systems -> mobile devices • One code tree can be executed on CPUs, GPUs, DSPs and hardware - Dynamically interrogate system load and balance work across available processors • OpenCL = Two APIs and C-based Kernel language - Platform Layer API to query, select and initialize compute devices - Kernel language - Subset of ISO C99 + language extensions - C Runtime API to build and execute kernels across multiple devices OpenCL KernelOpenCL CodeKernel OpenCL CodeKernel OpenCL CodeKernel Code GPU DSP CPU CPU HW © Copyright Khronos Group 2014 - Page 3 OpenCL Roadmap • What markets has OpenCL been aimed at? • What problems is OpenCL solving? • How will OpenCL need to adapt in the future? HPC HPC HPC Desktop HPC Discussion Desktop Desktop Mobile Focus for New Desktop Mobile Mobile Web Capabilities Mobile Web Web FPGA FPGA Embedded Safety Critical 3-component vectors Shared Virtual