aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorzqysara <zhangqiyu1@huawei.com>2018-06-01 16:57:41 +0800
committerzqysara <zhangqiyu1@huawei.com>2018-06-29 17:12:50 +0800
commit0f0f35db833679e2080fbdd824f214f3c6c0e5c3 (patch)
treeb49cd5ce9324346c0a70d7853ae26bac6b5477cb /README.md
parent24cbcfaa6fa1121dec1a029a1df114f065341156 (diff)
Introducing DMM README.md
Change-Id: Ia49a5a7be4981693bf0157501df0b4d4ca51025f Signed-off-by: zqysara <zhangqiyu1@huawei.com>
Diffstat (limited to 'README.md')
-rw-r--r--README.md53
1 files changed, 35 insertions, 18 deletions
diff --git a/README.md b/README.md
index a3005e0..de5c250 100644
--- a/README.md
+++ b/README.md
@@ -1,29 +1,27 @@
# 1. Introduction:
# ![nStack_Architecture](resources/nStack_Architecture.png "nStack_Architecture")
-
DMM (Dual Mode, Multi-protocol, Multi-instance) is a framework between applications
-and transport layer of networking stack. This framework can hosts different types of
-networking stack instances operating on different domains (kernel/user-space) or even with
+and transport layer of networking stack. This framework can host different types of
+networking stack instances operating on different domains (kernel/user-space) with
different protocol suites (TCP/IP, RDMA, or others). Application can use different type of
protocol stack implementations based on functional/performance requirements.
-
# 2. History:
Emerging applications are bringing extremely high-performance requirements to the
-network system. Eg. AR/VR, IOT etc. And Many of them coming with their unique demand
-of QOS/SLA. Some application need low latency network, some need high reliability etc.
+network system. Eg. AR/VR, IOT etc. And many of them come with their unique demand
+of QOS/SLA. Some applications need low latency network, some need high reliability etc.
Though such performance targets should be required for the complete communication system,
-the transport layer protocols play a key role and encountered a relatively higher
-challenge, because traditionally the TCP-based transport layer exploits the “best-effort” principle
-and provides no performance guarantees in its nature. However, as Internet applications rapidly
-grow and diversify, an all-powerful or one-fits-all protocol or algorithm becomes less feasible.
+the transport layer protocols play a key role and there are relatively bigger challenges,
+because traditionally the TCP-based transport layer exploits the “best-effort” principle
+and provides no performance guarantees by its nature. However, as Internet applications rapidly
+grow and diversify, all-powerful or one-fits-all protocol or algorithm become less feasible.
Thus, the traditional single-instance TCP-based network stack bears great challenges when
serving many applications with different QoS/SLA requirements simultaneously on the
-same platform. Also Moving the networking stack out of the kernel is an obvious trend in both
-the industry and literature. Technologies like DPDK, etc improving performance of network
+same platform. Also moving the networking stack out of the kernel is an obvious trend in both
+the industry and literature. Technologies, e.g. DPDK, improve performance of network
stack, by bypassing the kernel, avoiding context-switching and data copies, as well as providing
-a complete set of packet-processing acceleration libraries. Keeping above trends in mind the
+a complete set of packet-processing acceleration libraries. Keeping above trends in mind,the
DMM/nStack provides a framework where, system operators can plug in dedicated types of
networking stack instances according to performance and/or functional requirements from
the user space applications. Application doesn't have to worry about change their transport
@@ -32,17 +30,36 @@ instances and the app/socket-to-stack-mappings, which are provided via the orche
/management interface. So DMM provide a framework which can hide all the complexity of
different transport layer protocol and also provide the flexibility to choose a protocol stack
from manybased on functional/performance requirements.
-
-
# 3. Quick Start
Refer doc/Build_DMM.md
-
-
+# 4. Involved
+ * [Bi-Weekly DMM Metting.](https://wiki.fd.io/view/DMM/Meettng)
+ * [Join the DMM Mailing List.](https://lists.fd.io/g/dmm-dev)
+ * [Join fdio-dmm IRC channel.](https://wiki.fd.io/view/IRC)
+ * [Browse the code.](https://git.fd.io/dmm/tree/)
+ * [18.04 Release Plan](https://wiki.fd.io/view/Projects/dmm/Release_Plans/Release_Plan_18.04)
+
# 5. More Information
-
- https://wiki.fd.io/view/DMM
- https://wiki.fd.io/view/Project_Proposals/DMM
- Enabling “Protocol Routing”: Revisiting Transport Layer Protocol Design in Internet
Communications(http://ieeexplore.ieee.org/document/8114687/)
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+