User Tools

Site Tools


dpacc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
dpacc [2015/02/13 15:33]
Lingli Deng [Key Project Facts] committers & contributors
dpacc [2015/12/04 05:57]
Lingli Deng
Line 1: Line 1:
-====== Project: ​DPACC (Data Plane Acceleration) ======+====== Project: Data Plane Acceleration ​(DPACC) ======
  
 As a result of convergence of various traffic types and increasing data rates, the performance requirements (both in terms of bandwidth and real-time-ness) on data plane devices within network infrastructure have been growing at significantly higher rates than in the past. As the traditional ‘bump-in-the-wire’ network functions evolve to a virtualized paradigm with NFV, the focus will be even higher to deliver high performance within very competitive cost envelopes. At the same time, application developers have, in some cases, taken advantage of various hardware and software acceleration capabilities,​ many of which are platform supplier dependent. There is a clear impetus to move away from proprietary data plane interfaces, in favor of more standardized interfaces to leveraging the data plane capability of underlying platforms – whether using specialized hardware accelerators or general purpose CPUs.  As a result of convergence of various traffic types and increasing data rates, the performance requirements (both in terms of bandwidth and real-time-ness) on data plane devices within network infrastructure have been growing at significantly higher rates than in the past. As the traditional ‘bump-in-the-wire’ network functions evolve to a virtualized paradigm with NFV, the focus will be even higher to deliver high performance within very competitive cost envelopes. At the same time, application developers have, in some cases, taken advantage of various hardware and software acceleration capabilities,​ many of which are platform supplier dependent. There is a clear impetus to move away from proprietary data plane interfaces, in favor of more standardized interfaces to leveraging the data plane capability of underlying platforms – whether using specialized hardware accelerators or general purpose CPUs. 
Line 6: Line 6:
  
 The overall project plan for DPACC is: The overall project plan for DPACC is:
-  * .+  * Phase 1: (by 2015Q2) 
 +      - document typical VNF use-cases and high-level requirements for the generic functional abstraction for high performance data plane and acceleration functions, including hardware and software acceleration;​ and 
 +      - identify the potential extensions across various NFV interfaces and evaluate current state-of-art solutions from open-source upstream projects according to identified requirements and targeted framework. 
 + 
 +  * Phase 2: (by 2015Q4) 
 +      - specify detailed framework/​API design/​choice and document test cases for selected use-cases;​ 
 +      - provide open source implementation for both the framework and test tools; 
 +      - coordinate integrated testing and release testing results; and 
 +      - interface specification.
  
 Related wiki pages: Related wiki pages:
-  * [[dpacc/​dpacc_project_proposal| ​DPACC Project Proposal]] +  * [[dpacc/​dpacc_project_proposal| Project Proposal]] 
-  * [[dpacc/use_cases| Use Cases]] +  * [[https://​etherpad.opnfv.org/​p/dpacc_usecases| Use Cases]] 
-  * [[dpacc/dpacc_work_items|List of Candidate ​Work Items / Open Questions]]   +  * [[dpacc/dpacc_work_item| Work Items]] 
-  * [[dpacc/​meetings | Meeting Calendar]] +  * [[dpacc/​meetings | Meeting Calendar ​& Minutes]] ([[https://​global.gotomeeting.com/join/​647334949|Join]]
-  * [[dpacc/meeting_minutes ​Meeting Minutes]]+
  
 ---- ----
Line 19: Line 27:
  
 ** Project Creation Date: ** February 10, 2015 \\ ** Project Creation Date: ** February 10, 2015 \\
-** Category: ** Requirement \\+** Project ​Category: ** Requirement \\
 ** Lifecycle State: ** Incubation \\ ** Lifecycle State: ** Incubation \\
-** Primary Contact: **  \\ +** Primary Contact: ** Linli Deng (denglingli@chinamobile.com) ​\\ 
-** Project Lead: **  \\+** Project Lead: ** Lingli Deng (denglingli@chinamobile.com) ​\\
  
  
Line 28: Line 36:
  
   * Lingli Deng (China Mobile, denglingli@chinamobile.com)   * Lingli Deng (China Mobile, denglingli@chinamobile.com)
-  * Bob Monkman ​(ARM, Bob.Monkman@arm.com)+  * Ola Liljedahl ​(ARM, Ola.Liljedahl@arm.com)
   * Kin-Yip Liu (Cavium, Kin-Yip.Liu@caviumnetworks.com)   * Kin-Yip Liu (Cavium, Kin-Yip.Liu@caviumnetworks.com)
   * Xinyu Hu (Huawei, huxinyu@huawei.com)   * Xinyu Hu (Huawei, huxinyu@huawei.com)
   * Vincent Jardin (6WIND, vincent.jardin@6wind.com)   * Vincent Jardin (6WIND, vincent.jardin@6wind.com)
   * Wenjing Chu (DELL, Wenjing_Chu@DELL.com)   * Wenjing Chu (DELL, Wenjing_Chu@DELL.com)
-  * Saikrishna M Kotha (Xilinx, saikrishna.kotha@xilinx.com) 
   * Bin Hu (AT&T, bh526r@att.com)   * Bin Hu (AT&T, bh526r@att.com)
   * Subhashini Venkataraman (Freescale, subhaav@freescale.com)   * Subhashini Venkataraman (Freescale, subhaav@freescale.com)
Line 42: Line 49:
  
 ** Contributors:​ ** ** Contributors:​ **
 +  * Bob Monkman (ARM, Bob.Monkman@arm.com)
   * Peter Willis (British Telecom, peter.j.willis@bt.com)   * Peter Willis (British Telecom, peter.j.willis@bt.com)
-  * Fahd Abidi (EZCHIPfabidi@ezchip.com) +  * Fahd Abidi (Xilinxfahd.abidi@xilinx.com) 
-  * Deepak Unnikrishnan (deepak.cu@gmail.com)+  * Cyril Chemparathy (EZchip, cchemparathy@ezchip.com) 
 +  * Deepak Unnikrishnan (Altera, ​deepak.cu@gmail.com)
   * Julien Zhang (ZTE, zhang.jun3g@zte.com.cn)   * Julien Zhang (ZTE, zhang.jun3g@zte.com.cn)
-  * Srini Addepalli (Freescalesaddepalli@freescale.com)+  * Srini Addepalli (Intelsrinivasa.r.addepalli@intel.com)
   * François-Frédéric Ozog (6WIND, ff.ozog@6wind.com)   * François-Frédéric Ozog (6WIND, ff.ozog@6wind.com)
   * Tapio Tallgren (Nokia, tapio.tallgren@nsn.com)   * Tapio Tallgren (Nokia, tapio.tallgren@nsn.com)
   * Mikko Ruotsalainen (Nokia, mikko.ruotsalainen@nsn.com)   * Mikko Ruotsalainen (Nokia, mikko.ruotsalainen@nsn.com)
   * Zhipeng Huang (Huawei, huangzhipeng@huawei.com)   * Zhipeng Huang (Huawei, huangzhipeng@huawei.com)
-  * Argy Krikelis ​(Altera, ​AKRIKELI@altera.com)+  * Rabi Abdel (Altera, ​ahmrabi@altera.com)
   * Venky Venkatesan (Intel, Venky.Venkatesan@intel.com)   * Venky Venkatesan (Intel, Venky.Venkatesan@intel.com)
   * Alex Mui (ASTRI, alexmui@astri.org)   * Alex Mui (ASTRI, alexmui@astri.org)
   * Jesse Ai (ASTRI, jesseai@astri.org)   * Jesse Ai (ASTRI, jesseai@astri.org)
   * Arashmid Akhavain (Huawei, arashmid.akhavain@huawei.com)   * Arashmid Akhavain (Huawei, arashmid.akhavain@huawei.com)
-  * Mike Young (Huawei, myoung@wildernessvoice.com) 
   * Parviz Yegani (Juniper, pyegani@juniper.net)   * Parviz Yegani (Juniper, pyegani@juniper.net)
   * Mario Cho (hephaex@gmail.com)   * Mario Cho (hephaex@gmail.com)
   * Hongyue Sun (ZTE, sun.hongyue@zte.com.cn)   * Hongyue Sun (ZTE, sun.hongyue@zte.com.cn)
   * Haishu Zheng (ZTE, zheng.haishu@zte.com.cn)   * Haishu Zheng (ZTE, zheng.haishu@zte.com.cn)
 +  * Varun Sethi (Freescale, Varun.Sethi@freescale.com)
 +  * Bharat Mota (Freescale, bharat.mota@freescale.com)
 +  * Paul Kangil Choi (ETRI, forerunner@etri.re.kr)
 +  * John Bromhead (Cavium, John.Bromhead@caviumnetworks.com)
  
   ​   ​
Line 67: Line 79:
 ** Mailing List **: no dedicated mailing list - use opnfv-tech-discuss and tag your emails with [dpacc] in the subject for easier filtering \\ ** Mailing List **: no dedicated mailing list - use opnfv-tech-discuss and tag your emails with [dpacc] in the subject for easier filtering \\
 ** Meetings **:  ** Meetings **: 
-  * [[dpacc/​meetings | Meeting Calendar]]+  * [[dpacc/​meetings | Meeting Calendar ​& Minutes]] ([[https://​global.gotomeeting.com/​join/​470821909|Join]])
 ** Repository: ** dpacc ** Repository: ** dpacc
dpacc.txt · Last modified: 2016/02/09 13:48 by Michele Paolino