From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 11BBBF60C; Wed, 11 Jan 2017 19:51:43 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP; 11 Jan 2017 10:51:42 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,346,1477983600"; d="scan'208";a="1092846570" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga001.fm.intel.com with ESMTP; 11 Jan 2017 10:51:36 -0800 Received: from fmsmsx126.amr.corp.intel.com (10.18.125.43) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 11 Jan 2017 10:51:30 -0800 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.119]) by FMSMSX126.amr.corp.intel.com ([169.254.1.200]) with mapi id 14.03.0248.002; Wed, 11 Jan 2017 10:51:30 -0800 From: "Wiles, Keith" To: Vincent Li CC: "users@dpdk.org" , "dev@dpdk.org" Thread-Topic: [dpdk-users] Pktgen DPDK net bonding mode 4 802.3AD (LACP) not working with BIGIP trunk with LACP enabled Thread-Index: AQHSbDXBAKYhthw/v0OgGGadiN2LX6E0JSEA Date: Wed, 11 Jan 2017 18:51:30 +0000 Message-ID: <57835675-A430-40D9-83EC-6B5ADE66D247@intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.58.172] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Pktgen DPDK net bonding mode 4 802.3AD (LACP) not working with BIGIP trunk with LACP enabled X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 18:51:44 -0000 > On Jan 11, 2017, at 12:08 PM, Vincent Li wrote: >=20 > Hi, >=20 > I have direct two cable connections between Pktgen DPDK box and BIGIP >=20 > this is a problem I am not sure if it Pktgen, or the DPDK net bonding mod= e > 4 LACP, or the BIGIP trunk with LACP enabled issue, I am hoping someone > here have more clue and give me some direction on how to trouble shoot > this. I am suspecting there might some issue between DPDK net bonding > 8023ad mode 4 and BIGIP trunk LACP mode. I turned > on CONFIG_RTE_LOG_LEVEL=3DRTE_LOG_DEBUG and > defined RTE_LIBRTE_BOND_DEBUG_8023AD > in drivers/net/bonding/rte_eth_bond_8023ad.c hoping getting more debug > output in Pktgen, I could not see any debug output for 8023ad protocol. I am not going to be much help as I do not and have not used BIGIP. I assume you have the Pktgen that supports bonding mode 4. The previous Pkt= gen version would not call tx_burst() unless it had something to send, whic= h the bonding driver requires tx_burst() with zero packets at least at a gi= ven interval. The latest versions do call tx_burst() with zero pkts at leas= t within the needed timing. >=20 >=20 > packet tx/rx works : >=20 > 1 Pktgen with DPDK net bonding mode 1, 2, 3, 5 > 2 BIGIP trunk with LACP disabled (trunk port status UP) >=20 > packet tx/rx failed: >=20 > 1, Pktgen with DPDK net bonding mode 4 802.3AD > 2, BIGIP trunk with LACP enabled (trunk status is DOWN) >=20 > or > 1, Pktgen with DPDK net bonding mode 4 802.3AD > 2, BIGIP trunk with LACP disabled (trunk status is UP) >=20 > my end goal is to achieve 10G < througput < 20G with Pktgen DPDK net > bonding with Intel 82599 to load test BIGIP, so far with bonding mode 1, > 2,3, 5, I am unable to achieve throughput > 10G. Regards, Keith