Difference between revisions of "Project Proposals/DMM"

From fd.io
Jump to: navigation, search
(Project Contact Name and Email)
(Initial Committers)
Line 72: Line 72:
 
* [mailto:aa@bb.com Chang Qing] (LF ID)
 
* [mailto:aa@bb.com Chang Qing] (LF ID)
 
* [mailto:fanhongwei@huawei.com Fanhongwei] (LF ID  fanhongwei007)
 
* [mailto:fanhongwei@huawei.com Fanhongwei] (LF ID  fanhongwei007)
 +
* [mailto:ray.kinsella@intel.com Ray Kinsella] (LF ID  )
  
 
== Vendor Neutral ==
 
== Vendor Neutral ==

Revision as of 07:24, 11 January 2018


Name

Dual-Mode Multi-protocol Multi-instance (DMM)

Project Contact Name and Email

George Zhao <george.y.zhao@huawei.com>

Wangyalei <wangyalei2@huawei.com>

Repository Name

DMM

Description

This project DMM (Dual Mode, Multi-protocol, Multi-instance) aims to provide an extendable framework that supports different protocols on both kernel space and user space, with the DMM framework, system operators can plug-in dedicated types of networking stack instances according to performance and/or functional requirements from user applications, i.e. DMM framework hosts different types of networking stack instances operating on different domains (kernel space or user-space) and support for different protocol suits such as TCP/IP, RDMA, etc.


Dmm-framework.JPG

As shown in the above picture:

  • Applications use Posix compatible and uniform socket API library via system hijacking or LD_PRELOAD.
  • Neuro Resource Discovery (nRD) controls the set of protocol policies to route the packet. nRD continuously monitors the network state and updates the policy rules.
  • Local protocol orchestrator regularly syncs with nRD on policies.
  • Session layer of DMM (nSocket) lookups with protocol orchestrator for session request and manages the session mappings, based on the protocol lookup selects corresponding protocol stack.

Scope

The scope for DMM (Dual Mode, Multi-protocol, Multi-instance) is to provide a transport agnostic framework for the applications where applications can:

  • Work with both user space and kernel space network stack.
  • Use different network protocol stack based on their functional and performance requirement (QOS).
  • Work with multiple instances of transport protocol stack.
  • Engage or adopt new protocol stack dynamically.

Initial Committers

Vendor Neutral

No current or expected issues with vendor neutrality

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)