diff options
author | 2018-07-12 15:05:09 +0800 | |
---|---|---|
committer | 2018-07-30 02:57:33 +0000 | |
commit | 5b40b163195b59de61896c759694848ae93fb459 (patch) | |
tree | 0de615e39a44bee64fda7ca0635d180eb20e09f5 | |
parent | 6407560ec2d98a52b05b46513995483947110866 (diff) |
Fix: some typos
Delete personal information in nstack_socket.c.
Update Release Plan from 18.04 to 18.07.
Delete extra colons in README.md.
Change-Id: Ibcd15723a19887b54bd7a452a03ab56011112bc9
Signed-off-by: yexin <yexin13@huawei.com>
-rw-r--r-- | README.md | 28 | ||||
-rw-r--r-- | src/nSocket/nstack/nstack_socket.c | 2 |
2 files changed, 7 insertions, 23 deletions
@@ -1,13 +1,14 @@ -# 1. Introduction: +# 1. Introduction + +![nStack_Architecture](resources/nStack_Architecture.png "nStack_Architecture") -# ![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 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: +# 2. History Emerging applications are bringing extremely high-performance requirements to the 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. @@ -32,12 +33,13 @@ different transport layer protocol and also provide the flexibility to choose a 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) + * [18.07 Release Plan](https://wiki.fd.io/view/Projects/dmm/Release_Plans/Release_Plan_18.07) # 5. More Information - https://wiki.fd.io/view/DMM @@ -45,21 +47,3 @@ Refer doc/Build_DMM.md - Enabling “Protocol Routing”: Revisiting Transport Layer Protocol Design in Internet Communications(http://ieeexplore.ieee.org/document/8114687/) - - - - - - - - - - - - - - - - - - diff --git a/src/nSocket/nstack/nstack_socket.c b/src/nSocket/nstack/nstack_socket.c index 5841676..8fe493a 100644 --- a/src/nSocket/nstack/nstack_socket.c +++ b/src/nSocket/nstack/nstack_socket.c @@ -2386,7 +2386,7 @@ nstack_epoll_ctl (int epfd, int op, int fd, struct epoll_event *event) if (!epi) { ep_event.events |= (EPOLLERR | EPOLLHUP); // Check `man epoll_ctl` if you don't understand , smile :) - common_mem_rwlock_read_lock (get_fork_lock ()); /* to ensure that there is no fd to create and close when fork. added by tongshaojun t00391048 */ + common_mem_rwlock_read_lock (get_fork_lock ()); /* to ensure that there is no fd to create and close when fork. */ ret = nsep_epctl_add (ep, fd, &ep_event); common_mem_rwlock_read_unlock (get_fork_lock ()); } |