Difference between revisions of "Project Proposals/npu drivers"

From fd.io
Jump to: navigation, search
(Project Contact Name and Email)
(Project Contact Name and Email)
Line 7: Line 7:
 
== Project Contact Name and Email ==
 
== Project Contact Name and Email ==
 
[mailto:cference@inocybe.ca Calvin Ference], LF-ID: vezril
 
[mailto:cference@inocybe.ca Calvin Ference], LF-ID: vezril
More to determined.
 
  
 
== Repository Name ==
 
== Repository Name ==

Revision as of 14:28, 15 September 2016


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.

This will provide a central location for NPU vendors to provide open-source API's to their chips and allow an easy and extensible platform to enable SDN by integrating honeycomb and ODL into their solution with minimal effort on their end.

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)