From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <users-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 95F6146521 for <public@inbox.dpdk.org>; Mon, 7 Apr 2025 07:43:57 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 697B040156; Mon, 7 Apr 2025 07:43:57 +0200 (CEST) Received: from mail-yw1-f173.google.com (mail-yw1-f173.google.com [209.85.128.173]) by mails.dpdk.org (Postfix) with ESMTP id ACAF740DD7 for <users@dpdk.org>; Fri, 4 Apr 2025 16:08:35 +0200 (CEST) Received: by mail-yw1-f173.google.com with SMTP id 00721157ae682-6f74b78df93so26795157b3.0 for <users@dpdk.org>; Fri, 04 Apr 2025 07:08:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1743775715; x=1744380515; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=99f+aOEG6Veq6aRVc/z+e1ess1dYZ/riaJFEVKfRbms=; b=A0I5g73o1d6nwru2L7ws2TqWaJChsCimI9aDM7lLa+l2K+C3Cbd7saLtde0Gy822f6 O5ZAFUDjWgggvmu3u5ADydT1RbSrW7Hzm7GialjjRVPHzayIJNGOuJW4+aEBgS/m09Xj ySGQbhpxOtrOyhXmuFN6OF6nSu0mCd6HCr6Ncyb7TJ9sDxo+lHa0x8+MUv1mAxq3O3gY 1owwkCCmQsVpNGf76MbI1XGGcZvRZnrmpj5pnjjAA0YBwqBGf/hRUgf1irqULwWuOQbo AC9YHlUloW5dlrNmaEot7NhzlZCGm9t8/YBbEYo36WjUDw0UcSZTGWwrUQpZxNIHwIfr pxnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743775715; x=1744380515; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=99f+aOEG6Veq6aRVc/z+e1ess1dYZ/riaJFEVKfRbms=; b=Xv8fIEm0IazLbQBGwR/6eWJWvbLAhapufqBJRbEzcIkZL96nvWHp9vZK55Gaxxt+Ix QyHUXRT46LMOP5DZp6lfO9rwwWIhBIocDGXHvUechGiqUjKI1VkxwSL2E8ydN7e01Amx oHRRsSTZbCfxKj9GOHCBD1jSAE7baiwetmdnOGZ8CKdWS+ZP7LDt+/16xViyMNzjDU3b FCaICpBOtji1HJPuTAoqnBU64PrQ7rSc2XvZAviW3KVa12GPoDKMhCdvmqFqpG4CrDf9 jhqCtvcXsCzybG7EN44gKmZma2Y2DA6+Xv1Krl2wjaLBqH8XHKFylr9IMqSfy82eFiWX hz6A== X-Gm-Message-State: AOJu0YyDKCMAZwmlPRlS54OgNiZmM6hJdFkGokSowvi6Ew/TpygCWW24 dbsAviMvpPHkmnS+9JlAdjm8/+EUKbwvkcomnAxQBrCeQQmCelda0zcejLA0lmQQmoJ98baLr9X ADCyoUEd58hi9OOsGRjZ3HqEsbLOVpg== X-Gm-Gg: ASbGncuKf/sZt//EzrLe/mrQYBS0hemKC1K5z5Rp0pqMBf67axjX6VpzTLwxZ62VH0y zc1gWDkbGBFSC7rZefPlGaOWF18Oh+zkTl9bflu/HVW7bFtladKdT9hzG2KDZxdkWjbOv0XeQ86 wM/p4X4n3LA87/WOzIUD56b/JHlaQnKS3Ant2zaRRQRmnsjYJ0nEWc7RwCloo= X-Google-Smtp-Source: AGHT+IGiOjj+WguNWGOrWx9jCNx36vTblEozRdrRFDBhuNtBpeCyR0FbKgijf56o1by9aucRzCaMxsIqmRbbrjhLMNQ= X-Received: by 2002:a05:690c:6481:b0:702:627c:94ec with SMTP id 00721157ae682-703e3357786mr52866187b3.35.1743775714648; Fri, 04 Apr 2025 07:08:34 -0700 (PDT) MIME-Version: 1.0 From: Aman Thakur <r.aman.t.435@gmail.com> Date: Fri, 4 Apr 2025 19:38:23 +0530 X-Gm-Features: ATxdqUECDEnLmODh9LsQ-cGY5E0UTz02JQOhdU6rWR2kGVz6aeFHZ0EA8bUs970 Message-ID: <CAOUH2--o=L4gN-cKouohf3_fMCZ-tMOgs4eTGtkctV2e983v-g@mail.gmail.com> Subject: Bond fails to start all slaves To: users@dpdk.org Content-Type: multipart/alternative; boundary="0000000000000a2c530631f46c97" X-Mailman-Approved-At: Mon, 07 Apr 2025 07:43:56 +0200 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions <users.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/users>, <mailto:users-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/users/> List-Post: <mailto:users@dpdk.org> List-Help: <mailto:users-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/users>, <mailto:users-request@dpdk.org?subject=subscribe> Errors-To: users-bounces@dpdk.org --0000000000000a2c530631f46c97 Content-Type: text/plain; charset="UTF-8" Hi users, Environment =========== DPKD Version : 21.11.9 Bond member slave 1 : Intel e1000e I217 1Gbps "Ethernet Connection I217-LM 153a" slave 2 : Intel e1000e 82574 1Gbps "82574L Gigabit Network Connection 10d3" OS :Rocky Linux 8.10 rhel centos fedora Compiler: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-24) Steps to reproduce ================== 1. bind ports to dpdk dpdk-devbind.py -b vfio-pci 0000:b1:00.0 0000:b1:00.1 2. launch testpmd ./dpdk-testpmd -l 0-3 -n 4 -- -i --portmask=0x1 --nb-cores=2 --no-lsc-interrupt --port-topology=chained 3. create bonding device port stop all create bonded device 0 0 add bonding slave 0 2 add bonding slave 1 2 port start all show port info all Results: ======== the link status of 1 ports is down ( not specific to mode ) In every bond mode link speed of the slave interface 1 Intel e1000e I217 1Gbps "Ethernet Connection I217-LM 153a" is down. Port 0 Link down Port 1 Link up at 1 Gbps FDX Autoneg Port 1: link state change event Port 2 Link up at 1 Gbps FDX Autoneg Done Expected Result: ================ The status of all ports should be normal. Link status of both member/slave should be up and status of port 0 should not be always down. In mode 0 with bond mode 0 link speed should be 2 Gbps with 2 members each 1 1Gbps. *My Questions:* 1. What could be causing one of the slaves to become inactive ? 2. Is there a specific configuration or step I might be missing that's preventing the bond from utilizing both slaves ? 3. Are there any known compatibility issues or limitations with Intel e1000e I217 1Gbps "Ethernet Connection I217-LM 153a" that could explain this behavior? --0000000000000a2c530631f46c97 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div>Hi users, <br></div><div><br></div><= div>Environment<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>DPKD Version : 21.1= 1.9<br>Bond member <br>slave 1 : Intel e1000e I217 1Gbps "Ethernet Con= nection I217-LM 153a"<br>slave 2 : Intel e1000e 82574 1Gbps "8257= 4L Gigabit Network Connection 10d3"<br>OS :Rocky Linux 8.10 rhel cento= s fedora<br>Compiler: =C2=A0gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-24)<br>= <br>Steps to reproduce<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D<br>1. bind ports to dpdk <br>dpdk-devbind.py -b vfio-pci 0000:b1:00.= 0 0000:b1:00.1<br>2. launch testpmd<br>./dpdk-testpmd -l 0-3 -n 4 -- -i --p= ortmask=3D0x1 --nb-cores=3D2 --no-lsc-interrupt --port-topology=3Dchained<b= r>3. create bonding device<br>port stop all<br>create bonded device 0 0<br>= add bonding slave 0 2<br>add bonding slave 1 2<br>port start all<br>show po= rt info all<br><br><br><br>Results: <br>=3D=3D=3D=3D=3D=3D=3D=3D<br>the lin= k status of 1 ports is down ( not specific to mode )<br>In every bond mode = link speed of the slave interface 1 Intel e1000e I217 1Gbps "Ethernet = Connection I217-LM 153a" is down.<br><br>Port 0 Link down<br>Port 1 Li= nk up at 1 Gbps FDX Autoneg<br><br>Port 1: link state change event<br>Port = 2 Link up at 1 Gbps FDX Autoneg<br>Done<br><br>Expected Result:<br>=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>The status of all ports shoul= d be normal. Link status of both member/slave should be up and status of po= rt 0 should not be always down. <br>In mode 0 with bond mode 0 link speed s= hould be 2 Gbps with 2 members each 1 1Gbps.</div><div><br></div><div> <p><b>My Questions:</b></p><ol><li>What could be causing one of the slaves = to become inactive ?</li><li>Is there a specific configuration or step I mi= ght be missing that's=20 preventing the bond from utilizing both slaves ?</li><li>Are there any know= n compatibility issues or limitations with=20 Intel e1000e I217 1Gbps "Ethernet Connection I217-LM 153a"=C2=A0 = that could explain this behavior?</li></ol> <br></div><div><br></div> </div> </div> --0000000000000a2c530631f46c97--