From owner-svn-doc-head@freebsd.org Sun Oct 18 02:29:36 2015 Return-Path: Delivered-To: svn-doc-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2724A10F62; Sun, 18 Oct 2015 02:29:36 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F215385; Sun, 18 Oct 2015 02:29:36 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id t9I2TZeR079876; Sun, 18 Oct 2015 02:29:35 GMT (envelope-from bjk@FreeBSD.org) Received: (from bjk@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id t9I2TZKl079875; Sun, 18 Oct 2015 02:29:35 GMT (envelope-from bjk@FreeBSD.org) Message-Id: <201510180229.t9I2TZKl079875@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bjk set sender to bjk@FreeBSD.org using -f From: Benjamin Kaduk Date: Sun, 18 Oct 2015 02:29:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r47613 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Oct 2015 02:29:37 -0000 Author: bjk Date: Sun Oct 18 02:29:35 2015 New Revision: 47613 URL: https://svnweb.freebsd.org/changeset/doc/47613 Log: Add MPTCP report from Nigel Williams Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Sun Oct 18 01:16:34 2015 (r47612) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Sun Oct 18 02:29:35 2015 (r47613) @@ -2742,4 +2742,81 @@ + + Multipath TCP for &os; + + + + + Nigel + Williams + + njwilliams@swin.edu.au + + + + + MPTCP for &os; + Project Website + MPTCP + for &os; Source Repository + + + +

Multipath TCP (MPTCP) is an extension to TCP that allows + for the use of multiple network interfaces on a standard TCP + session. The addition of new addresses and scheduling of data + across these occurs transparently from the perspective of the TCP + application.

+ +

The goal of this project is to deliver an MPTCP kernel + patch that interoperates with the reference MPTCP implementation, + along with additional enhancements to aid network research.

+ +

The v0.5 patch was released, which is the first patch + of the re-written implementation. We are in the process of + documenting the new design and addressing some feedback as + provided from the community.

+ +

Work has commenced on improved input handling, as the current + method of receiving and reassembling segments has been the cause + of some instability/stalls during connection shutdown. This will + involve re-using the subflow receive buffers and an upcall to + enqueue a MP-layer reassembly task without the need to take a lock + on the MP control block. The improvements should also allow + bypassing mptcp_usrreq for standard TCP connections.

+ +

The MPTCP commit history was synchronized with + hg-beta.FreeBSD.org, and have made the repository available on + BitBucket (see links). Future patch releases will be tagged + there. The tree is now merged with &os; head weekly. An updated + v0.51 patch is ready for release. +

+ + + + The FreeBSD Foundation + + + + +

Release the v0.51 patch.

+ + + +

Populate documentation and the issue tracker on the BitBucket + repository.

+ + + +

Improvements to receive-side code before further testing.

+ + + +

Prepare a technical report detailing the design of the current + patch.

+ + + +