Difference between revisions of "Project Proposals/npu drivers"
From fd.io
(Created page with "Category:Project Proposal <!-- Please note: fd.io code is to be licensed under the Apache 2.0 license unless an exception is approved by the board --> == Name == NPU Driv...") |
(→Scope) |
||
| Line 16: | Line 16: | ||
== Scope == | == Scope == | ||
The FD.io NPU Drivers scope is: | The FD.io NPU Drivers scope is: | ||
| − | + | * The project will include packaging the necessary vendor specific libraries for their NPU. | |
| − | + | * The project will include the drivers for passing VPP API messages to a specific NPU. | |
== Initial Committers == | == Initial Committers == | ||
Revision as of 17:36, 24 August 2016
Contents
Name
NPU Drivers support for FD.io VPP.
Project Contact Name and Email
Calvin Ference, LF-ID: vezril
Repository Name
npu
Description
NPU Drivers project will focus on providing multi-vendor NPU support (Cavium, Broadcom, etc) into VPP to provide hardware acceleration.
Scope
The FD.io NPU Drivers scope is:
- The project will include packaging the necessary vendor specific libraries for their NPU.
- The project will include the drivers for passing VPP API messages to a specific NPU.
Initial Committers
Calvin Ference, LF-ID: vezril
Vendor Neutral
NPU vendors who wish to provide hardware acceleration for their products will have to provide open source libraries to interface with.
Meets Board Policy (including IPR, being within Board defined Scope etc)
Meets board policy as expressed in Technical Community Charter and IP Policy
Administrata
- Request for Project proposal consideration
- Email: (place link to email to TSC proposing project, this can be obtained from TSC Archives
- Date: (date proposed, makes it simpler to calculate the pre-requisite 2 week time period of gestation before being permitted to be voted on)
