/
Breakout Session on Where to Position Accelerators in the S Breakout Session on Where to Position Accelerators in the S

Breakout Session on Where to Position Accelerators in the S - PowerPoint Presentation

olivia-moreira
olivia-moreira . @olivia-moreira
Follow
390 views
Uploaded On 2017-09-24

Breakout Session on Where to Position Accelerators in the S - PPT Presentation

Peter Hofstee Eliezer Levy Pinar Tozun Babak Falsafi Margo Seltzer Henning Funke Ken Eguro Markus Dreseler Gilles Pokam Zsolt Istvan Codesign App DB ID: 590222

context accelerator data app accelerator context app data platform definition hardware api access switch internal specific

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Breakout Session on Where to Position Ac..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Breakout Session on Where to Position Accelerators in the Stack

Peter

Hofstee

,

Eliezer

Levy, Pinar

Tozun

,

Babak

Falsafi

, Margo Seltzer, Henning

Funke

, Ken

Eguro

, Markus

Dreseler

, Gilles

Pokam

, Zsolt

IstvanSlide2

Codesign

App

DB

OS

Network

Storage

Mem

Platform

ProcSlide3

Accelerator

Definition

A piece of specialized hardware, non-critical, but improves efficiency

Must exist in platform!OS arbitrates access to, directly accessible to everyone (all apps can be aware of what accelerator is and what it does)Slide4

OS must be able to

context switch accelerator configuration

context switch internal state

know multiplexing rules

App must be able toApplication-specific code (initialization, task specification, closure)What data to use for input, where to put outputSlide5

Accelerator API

The right API is context/accelerator-specific

How to we give accelerator access to data? Virtual memory? Pinned pages?

Does the accelerator have independence to schedule its own work?

Called synchronously or asynchronouslySlide6

Level of abstraction should be defined such that it exposes as much internal details as needed, but not too much such that it becomes cumbersome. This is dependent on the native

datatypes

/operations of the app and the “efficiency” (both in terms of literal things like bandwidth and conceptual things like “natural” data types) of the communication. This is the definition of hardware/software co-design.Slide7

None

Percent of workload (Amdahl fraction)

Benefit

Programmable

Fabric

ASIC