From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 16BA146527 for ; Mon, 7 Apr 2025 12:05:55 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CE60940156; Mon, 7 Apr 2025 12:05:54 +0200 (CEST) Received: from mail-oa1-f54.google.com (mail-oa1-f54.google.com [209.85.160.54]) by mails.dpdk.org (Postfix) with ESMTP id 8D5FE40150 for ; Mon, 7 Apr 2025 12:05:53 +0200 (CEST) Received: by mail-oa1-f54.google.com with SMTP id 586e51a60fabf-2c7b2c14455so2844948fac.2 for ; Mon, 07 Apr 2025 03:05:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744020352; x=1744625152; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/+GhMgGY1KhVRqqM09hb7Pvkx93wkIHoRi1VLqTdkMM=; b=TxeiIyDOr6QBUfZIlwTR0vTxuJR/STHn3rBhRyBGGF0tAzZsadYbPcJUIjR1K/Xu01 8O7NSaqHJTh22/lEjRkU7De6sUBE1+ajjWxQZI4QBwK4wgAJnPEW18JU/lAF5khbkcNT 5UO1PtuEP+B14GrWTcjJdfjg6hgNhVJCaWxqbZiKAidrPDCgT+B3VrMHQLHyFZNjKrk2 K4BMuSIboCy6H0ck5MdWXlljJRBXL1SsBDrU7T1zRVDaFRdM5r75ODGU4Nkg5OKQBAbr Uzqv3YU57hvAvVjsm/1oEBfzHYvzN2mwmf1h5X3oXr6qZhdV2lyh+pb54E8x57WM66gq vqMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744020352; x=1744625152; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/+GhMgGY1KhVRqqM09hb7Pvkx93wkIHoRi1VLqTdkMM=; b=GZ0e1++lzV2lwrXpm4wRbywd3FD6JZ8kvmR7cEy5QJmlNv2jxsWu3MSPvtCpd1SJRv LIb2F8Ou3I9xByyEKGTQ2mCerQvldcQCD/ULTEJIiRyrkCfwW1twim9V8UMv+GcP7GOz GSN/MUSxa+mLpD50tUo/IAFX8Hkcg2DyKAP4itWwOXIA7huQ2VSTfY65V7WuOKoG47ui aCvMD/VFOphMkXt+WnJRfFQaWN1pVxhGGB2JbD/ty9nzcOrRn0zqUCqCHvQtsfOQ9xls PJj0rvpR1eKys77oB2vq70xgX87oV2wDbytRNbkekFfQEIAZaVerfvQOThP2omRzrryX vKLg== X-Gm-Message-State: AOJu0Yz6LROvQeRmIKOTs0+8YjgGWF3fBJFcamBWNGTw5Gz9IcML12af UK3KDgNgHNLUB1sjRST+CttNxO5iswk1XIM+B66ZcJR4s4ETFLbC2ZjOacEsYeK/ce9AfC1TByA YcfMDG+FTQoQ0pIWukaL6+Ue8a8Y= X-Gm-Gg: ASbGncv3Bi9RwtO44rQlOlblJlPiGisRQiihpdEhZqsEQ4IFXJu25ifCwtJMllCQr5C SGQszmp9Tsmnm3hhW6rZSLP9lxTy8CovmU65IMS4VjB6D1+5OtUvbeNILHlh36ErZs0QoXb5z03 BxCWEpK/WD3nyl3Vm5Lc958BdVTPlByj733M3EgadiUtPSJc3k+Us1BFhyzkHz X-Google-Smtp-Source: AGHT+IGoekIQe2KoZMgcQgkTFqbi7UALhFI8E2hGnII0496vEfTbEpWgwL9eJ+ZBqZ1fDvXuQ3CQzHa6vpaUHomDlJA= X-Received: by 2002:a05:6870:ff88:b0:297:2719:deb6 with SMTP id 586e51a60fabf-2cc9e5056a8mr6345170fac.1.1744020352598; Mon, 07 Apr 2025 03:05:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: madhukar mythri Date: Mon, 7 Apr 2025 15:35:41 +0530 X-Gm-Features: ATxdqUESCFmf22n5pN3PK23UMy091gv-2hwSSStV0aDsid8US3nVQ1bwd0S5qpM Message-ID: Subject: Re: Bond fails to start all slaves To: Aman Thakur Cc: users@dpdk.org Content-Type: multipart/alternative; boundary="000000000000990c3206322d61b5" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000990c3206322d61b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Why is the EAL argument "portmask" set to 0x1 ? it optional, try by removing it. Have you tried without "--no-lsc-interrupt" from EAL arguments. And also, you can cross checked the Bonding device creation and configuration with the "--vdev" EAL parameters as follows: --vdev 'net_bonding0,mode=3D0,member=3D0000:b1:00.0,member=3D0000:b1:00.1' Regards, Madhukar. On Mon, Apr 7, 2025 at 1:40=E2=80=AFPM Aman Thakur = wrote: > Hi users, > > Environment > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 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 10d= 3" > OS :Rocky Linux 8.10 rhel centos fedora > Compiler: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-24) > > Steps to reproduce > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 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=3D0x1 --nb-cores=3D2 > --no-lsc-interrupt --port-topology=3Dchained > 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: > =3D=3D=3D=3D=3D=3D=3D=3D > 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: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > The status of all ports should be normal. Link status of both member/slav= e > 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 eac= h > 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 expla= in > this behavior? > > > > --000000000000990c3206322d61b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Why is the EAL argument "portm= ask" set=C2=A0to 0x1 ? it optional, try by removing it.
Have= you tried without "--no-lsc-interrupt" from EAL arguments.
=
And also, you can cross checked the Bonding device creation and config= uration with the "--vdev" EAL parameters as follows:

--vdev 'net_bonding0,mode=3D0,member=3D0000= :b1:00.0,member=3D0000:b1:00.1'


Reg= ards,
Madhukar.

On Mon, Apr 7, 2025 at= 1:40=E2=80=AFPM Aman Thakur <= r.aman.t.435@gmail.com> wrote:
Hi users,
=

Environment
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<= br>DPKD Version : 21.11.9
Bond member
slave 1 : Intel e1000e I217 1G= bps "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: =C2=A0gcc (GCC) 8.5.0 20210514 = (Red Hat 8.5.0-24)

Steps to reproduce
=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
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=3D0x1 --nb-cores=3D2 --no-lsc-interrupt --port= -topology=3Dchained
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:
=3D=3D=3D=3D= =3D=3D=3D=3D
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 I21= 7 1Gbps "Ethernet Connection I217-LM 153a" is down.

Port 0= Link down
Port 1 Link up at 1 Gbps FDX Autoneg

Port 1: link stat= e change event
Port 2 Link up at 1 Gbps FDX Autoneg
Done

Expec= ted Result:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The stat= us of all ports should be normal. Link status of both member/slave should b= e up and status of port 0 should not be always down.
In mode 0 with bon= d 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 mi= ght be missing that's=20 preventing the bond from utilizing both slaves ?
  3. 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?


--000000000000990c3206322d61b5--