From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 5D8151B303 for ; Thu, 18 Jan 2018 15:15:00 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0CB2420CC5; Thu, 18 Jan 2018 09:15:00 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 18 Jan 2018 09:15:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ojgWOxTTdqXatVsIVwfRL7Da5/ z3FsOnP8aActvLc/o=; b=CRkYoJ5i3gG3Agc7hO9MYFWZKy/XXgXaOSiRDWkndj H8GgRUYGCY0Aw3d5svw2iDioco9Q98hzbzntKgZpKwo3x0Q31LYbzduvHIl/o8WX wue5xuQA2bDeoFeelj1sTKFN+7noRL73/JiPTDNSrt4I08JHIIgqNG6C7pYCydRs Q= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ojgWOx TTdqXatVsIVwfRL7Da5/z3FsOnP8aActvLc/o=; b=kkNcu1dM3aAx0D0X9kcUF/ 1Muuto1aQObPj8jhcTQQcBKey3MTrqK7gnF+kdxTdRkxqpRRoeVLuFIXxu4GRKlB xFcIK48ZN/l3CffcNWfkM026bOQ1+m/lfh+hXSUHO6LxPcE12s801H+zwf6uOAIS uDV7LDjhGHliZx51swzjP5rS+8bEE6yqumQcfzFMGurTG6TKe/K2Jo4Y87Dlyib/ QjSF+KpMkpPLDVInKqXcUao+EfsxXJjih0HJbw2fQLW9TqCtDKgXKZEFRZgYuqyd naoQjaAuIoKvvN1wE2a2gSafdLag8ag0YqhEhkNOW0yH22DE5G1vqqeSy2ZP1VSg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9D738246E6; Thu, 18 Jan 2018 09:14:59 -0500 (EST) From: Thomas Monjalon To: users@dpdk.org Cc: =?utf-8?B?0JDQu9C10LrRgdC10Lkg0KLQtdC70Y/RgtC90LjQutC+0LI=?= , declan.doherty@intel.com Date: Thu, 18 Jan 2018 15:14:26 +0100 Message-ID: <14062498.R1q8Tvprge@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-users] Does BONDING_MODE_8023AD is works in 17.11? 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: Thu, 18 Jan 2018 14:15:00 -0000 No reply after 2 months, adding maintainer Cc. 17/11/2017 23:24, =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9 =D0=A2=D0=B5= =D0=BB=D1=8F=D1=82=D0=BD=D0=B8=D0=BA=D0=BE=D0=B2: > Greetings. I have issue with link-aggregation in DPDK. My HP A5820X=20 > switch does not recive LACP from DPDK application. >=20 > Has anyone worked with BONDING_MODE_8023AD? >=20 > I have: DPDK 17.11 HEAD & 11.1-RELEASE-p4 FreeBSD >=20 > Also I build examples/bond with little changes: >=20 > --- a/examples/bond/main.c > +++ b/examples/bond/main.c > @@ -226,7 +226,7 @@ bond_port_init(struct rte_mempool *mbuf_pool) > uint16_t nb_rxd =3D RTE_RX_DESC_DEFAULT; > uint16_t nb_txd =3D RTE_TX_DESC_DEFAULT; >=20 > - retval =3D rte_eth_bond_create("bond0", BONDING_MODE_ALB, > + retval =3D rte_eth_bond_create("net_bonding0", BONDING_MODE_8023A= D, > 0 /*SOCKET_ID_ANY*/); > if (retval < 0) > rte_exit(EXIT_FAILURE, >=20 > Run it: >=20 > $ sudo build/bond_app > EAL: Sysctl reports 16 cpus > EAL: Detected 16 lcore(s) > EAL: Contigmem driver has 1 buffers, each of size 32GB > EAL: Mapped memory segment 1 @ 0x8023ff000: physaddr:0x800000000, len=20 > 34359738368 > EAL: PCI device 0000:03:00.0 on NUMA socket 0 > EAL: probe driver: 8086:1521 net_e1000_igb > EAL: 0000:03:00.0 not managed by UIO driver, skipping > EAL: PCI device 0000:03:00.3 on NUMA socket 0 > EAL: probe driver: 8086:1521 net_e1000_igb > EAL: 0000:03:00.3 not managed by UIO driver, skipping > EAL: PCI device 0000:05:00.0 on NUMA socket 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:05:00.1 on NUMA socket 0 > EAL: probe driver: 8086:10fb net_ixgbe > User device list: > PMD: ixgbe_dev_link_status_print(): Port 0: Link Down > Port 0 MAC: 90:e2:ba:d0:a3:c4 > PMD: ixgbe_dev_link_status_print(): Port 1: Link Down > Port 1 MAC: 90:e2:ba:d0:a3:c5 > EAL: Initializing pmd_bond for net_bonding0 > PMD: Using mode 4, it is necessary to do TX burst and RX burst at least=20 > every 100ms. > EAL: Create bonded device net_bonding0 on port 2 in mode 4 on socket 0. > PMD: ixgbe_dev_link_status_print(): Port 0: Link Down > PMD: ixgbe_dev_link_status_print(): Port 1: Link Down > Port 2 MAC: 90:e2:ba:d0:a3:c4 > Starting lcore_main on core 1:0 Our IP:7.0.0.10 > bond6>show > 90:e2:ba:d0:a3:c4 > 90:e2:ba:d0:a3:c5 > Active_slaves:0 packets received:Tot:0 Arp:0 IPv4:0 >=20 > Active slaves always 0. I tried configure bond in testpmd. Same problem. >=20 > On the switch all ports is in up state but: >=20 > Received LACP Packets: 0 packet(s) >=20 >=20