[multipathtcp] how to deal with GRO when we use MPTCP?

王帅 <13211134@bjtu.edu.cn> Wed, 22 March 2017 07:31 UTC

Return-Path: <13211134@bjtu.edu.cn>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34BA612947C for <multipathtcp@ietfa.amsl.com>; Wed, 22 Mar 2017 00:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level:
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L4=0.001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16T9ojEKCTdy for <multipathtcp@ietfa.amsl.com>; Wed, 22 Mar 2017 00:31:45 -0700 (PDT)
Received: from bjtu.edu.cn (mail.bjtu.edu.cn [218.249.29.198]) by ietfa.amsl.com (Postfix) with ESMTP id A6F2D129526 for <multipathtcp@ietf.org>; Wed, 22 Mar 2017 00:31:41 -0700 (PDT)
Received: by ajax-webmail-Jdweb2 (Coremail) ; Wed, 22 Mar 2017 15:32:21 +0800 (GMT+08:00)
Date: Wed, 22 Mar 2017 15:32:21 +0800 (GMT+08:00)
From: =?GBK?B?zfXLpw==?= <13211134@bjtu.edu.cn>
To: multipathtcp <multipathtcp@ietf.org>
Message-ID: <2e5562a3.3efcf.15af4ee489c.Coremail.13211134@bjtu.edu.cn>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_935518_114235594.1490167941274"
X-Originating-IP: [124.127.174.24]
X-Priority: 3
X-Mailer: Coremail Webmail Server Version 4.0.8 dev build 20150608(70565.7215.7117) Copyright (c) 2002-2017 www.mailtech.cn bjtu
X-SendMailWithSms: false
X-CM-TRANSID: M55wygAX+rKFKNJYiZPCAA--.60361W
X-CM-SenderInfo: yrtsiiartuquxmwxhvlgxou0/1tbiAg0HA1RyqAXVLgABs6
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/4FYY4O06RrQST48znmbzzmkDuOI>
X-Mailman-Approved-At: Wed, 22 Mar 2017 01:11:50 -0700
Subject: [multipathtcp] how to deal with GRO when we use MPTCP?
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 07:31:47 -0000

Hi,


     Some NICs has GRO(generic-receive-offload), which works by aggregating multiple incoming packets from a single stream into a larger buffer before they are passed higher up the networking stack, thus reducing the number of packets that have to be processed. But when we use MPTCP, GRO may aggregate packets whose subflow sequence number is continuous but data sequence number is discontinuous. This is not expected. How can we deal with this problem? Is it necessary to disable GRO?


Best wishes,
Wang Shuai