From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 9C8A25A49 for ; Wed, 5 Aug 2015 10:29:06 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP; 05 Aug 2015 01:29:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,615,1432623600"; d="scan'208,217";a="619617617" Received: from pgsmsx106.gar.corp.intel.com ([10.221.44.98]) by orsmga003.jf.intel.com with ESMTP; 05 Aug 2015 01:29:04 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by PGSMSX106.gar.corp.intel.com (10.221.44.98) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 5 Aug 2015 16:29:03 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.38]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.188]) with mapi id 14.03.0224.002; Wed, 5 Aug 2015 16:29:01 +0800 From: "Liu, Yong" To: "Fan, ChangruX" , "dts@dpdk.org" Thread-Topic: fix an issue in ipv4_reassembly Thread-Index: AdDPWIpI69TZvrbEQri29eLpauki5QAABesg Date: Wed, 5 Aug 2015 08:29:00 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10EB55D4@SHSMSX103.ccr.corp.intel.com> References: <84799DAADE9E2A44834F0D0FF8A61A911CC95675@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <84799DAADE9E2A44834F0D0FF8A61A911CC95675@SHSMSX101.ccr.corp.intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dts] fix an issue in ipv4_reassembly X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2015 08:29:07 -0000 Thanks, Changru. I think it's the root cause of the failure. From: Fan, ChangruX Sent: Wednesday, August 05, 2015 4:27 PM To: Liu, Yong; dts@dpdk.org Cc: Chen, WeichunX Subject: fix an issue in ipv4_reassembly Hi Liu, Yong The case send_4K_frames_split_in_7_and_4K_maxflows which in ipv4_= reassembly is failed on freebsd10.1. I think the reason is that, in the function set_max_num_of_fragments it's = set with an error configuration file. Please check the patch. Thank, changru