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 920F942923; Wed, 12 Apr 2023 08:56:58 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 58FC44111C; Wed, 12 Apr 2023 08:56:54 +0200 (CEST) Received: from mx0b-00169c01.pphosted.com (mx0b-00169c01.pphosted.com [67.231.156.123]) by mails.dpdk.org (Postfix) with ESMTP id AE91A40A7E for ; Mon, 3 Apr 2023 11:23:42 +0200 (CEST) Received: from pps.filterd (m0048188.ppops.net [127.0.0.1]) by mx0b-00169c01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3336VFPO006208 for ; Mon, 3 Apr 2023 02:23:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : cc : content-type; s=PPS12012017; bh=c0BGFE/Ai8LzZHu42I+gYxzCDG9ZrOxk8olQcMzyB6I=; b=Fx6BM9u9UF/1vatovRkif3ac9ff0cv/lABngamhxvhPo0FSOnearYa49hrwbAfFcvwgw UNUJ5hAIR1QumjhQx6NExNViYfBSwUWR02omcqmaq0UZ0k38zBCcpOp5VbOqytkAne4j 771pcZKdbNvRPGD0NGQvh0HHk2OdGcUcLTdyP4BN+wSC1ahAWllhMFrwng4dUS5227ep s5sh76EDAjc0IQhzRHM4WzI9EOgLZk/gNLdTodw+T1uFnkGvq8FnGMGsBtsvYBxE7IoJ To3XkqNb5PgX87LG0OAH3NuwBYm+flBpqNUDO7IBp1IbvRrhM+LSDfqMG0CJVkbs5NP2 8g== Received: from mail-vs1-f69.google.com (mail-vs1-f69.google.com [209.85.217.69]) by mx0b-00169c01.pphosted.com (PPS) with ESMTPS id 3ppg9dufcn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 03 Apr 2023 02:23:41 -0700 Received: by mail-vs1-f69.google.com with SMTP id a25-20020a67ca99000000b004267e7dacccso9583703vsl.16 for ; Mon, 03 Apr 2023 02:23:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks.com; s=google.paloaltonetworks.com; t=1680513804; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c0BGFE/Ai8LzZHu42I+gYxzCDG9ZrOxk8olQcMzyB6I=; b=XJOW637LUocwhZdGBd4yB0WdXfMC9xiL5dT3ERZ+rU5juBx26syHknm466GHMZnxMT NgOL3OHTydgDP2DBQUQntBZZJ97xse1U9N1Q8OmIo/bSIfgCWs82f1zHaNqNu8ZDV7xJ wu7vljeLz8FZO+TkPBz2xJ4CsWN0qWvhiZZnmyxjQ480xgXzMXmJ+bbVfL1pYGumzNhR YshkazxBnIgl9Rx0jkcVK2Ba9cL6psf7HtkXvJ98DtqzIw8uBju24AFrZ4SdniJUC7Rc RsTa7HRSJ/vbMnDoIeWWNiaFglVY4w7MWcEN4tZE58T+2fBgiEXYjlWbIRV+mfvi1z/J 88Nw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680513804; 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=c0BGFE/Ai8LzZHu42I+gYxzCDG9ZrOxk8olQcMzyB6I=; b=MYwYQXy0hWk9eHaYhRFP1zNbCHgmflJouLKVGVqopfdjI3dCPCBAPv55iZS+u2SWkY t6NxXXOaiz3Nxn9iEzD3suC6sXkUCMKnB2i68oZf5JVlNVARYQfPZftd9vNah2lQwtHm Rx7JtqhKv/BmEHhLVxy88/FIB0n0BhiUKEvtSLGwybgJjx8+9fpGOvcZ/JBbc+el+wlB qxUmDDZPTkHAj61zwh6m++cPvOqCuzkQ33u4H5Dm2fZVujBeWVBZdelKINyaqaDWZ0+i cxysgg46SbmJPh15verpFgc8RsCL+8svOIjgSc/G9VpEbfMR/MiNH7z6HFtYeP89Igto y0xQ== X-Gm-Message-State: AAQBX9erHbbouRt79ajFc2M3jhD69Q5d5YtOxpWnCRLW5qD+/2Ww48Ir jLypIJ8WgrQimskrbwmMKp6In//YauBlAXI+R4O8K4iQyWGHeyM056/SHATp0wgwClubIDMYN9X cFSWfDJW/MpLrDtl2zjc= X-Received: by 2002:a67:d309:0:b0:423:e2c4:351e with SMTP id a9-20020a67d309000000b00423e2c4351emr19925921vsj.6.1680513804299; Mon, 03 Apr 2023 02:23:24 -0700 (PDT) X-Google-Smtp-Source: AKy350Y+9wrDLr1Dz2K1IFNmSaTcoaLELMK7IlvuLqqcjX1aD/fdMrUqlT5sw+UIsfo5M2DJXw5wOhvu0SWpCpy54lU= X-Received: by 2002:a67:d309:0:b0:423:e2c4:351e with SMTP id a9-20020a67d309000000b00423e2c4351emr19925914vsj.6.1680513803979; Mon, 03 Apr 2023 02:23:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Amiya Mohakud Date: Mon, 3 Apr 2023 14:53:11 +0530 Message-ID: Subject: Re: [Bug 1209] vmxnet3 interface not receiving any packets with dpdk-22.11.1 To: David Marchand Cc: Jochen Behrens , dev@dpdk.org, pagupta@vmware.com Content-Type: multipart/alternative; boundary="00000000000053c22a05f86b1c99" X-Proofpoint-ORIG-GUID: 25vdL9hGJtFMCWl-zaXuN6IaOx1EsWeC X-Proofpoint-GUID: 25vdL9hGJtFMCWl-zaXuN6IaOx1EsWeC X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-04-03_06,2023-03-31_01,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 lowpriorityscore=0 mlxlogscore=768 suspectscore=0 priorityscore=1501 mlxscore=0 bulkscore=0 adultscore=0 impostorscore=0 spamscore=0 clxscore=1011 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2304030072 X-Mailman-Approved-At: Wed, 12 Apr 2023 08:56:51 +0200 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --00000000000053c22a05f86b1c99 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jochen, Could you please help here? Regards Amiya On Fri, Mar 31, 2023 at 1:10=E2=80=AFPM David Marchand wrote: > Hello Jochen, > > On Fri, Mar 31, 2023 at 9:07=E2=80=AFAM wrote: > > > > Bug ID 1209 > > Summary vmxnet3 interface not receiving any packets with dpdk-22.11.1 > > Product DPDK > > Version 22.11 > > Hardware x86 > > OS All > > Status UNCONFIRMED > > Severity critical > > Priority Normal > > Component ethdev > > Assignee dev@dpdk.org > > Reporter amohakud@paloaltonetworks.com > > Target Milestone --- > > > > Hi, > > I recently upgraded our DPDK to 22.11.1 and observed that the guest > vmxnet3 > > interface is not receiving any unicast packets. It's able to receive th= e > > broadcast packets though. We enable promiscuous and all-multicast on th= e > port. > > > > rte_eth_promiscuous_enable(port); > > rte_eth_allmulticast_enable(port); > > > > This happens when the vswitch has only 2 ports attached. > > > > On further triaging, > > - I could find out that on the same setup, dpdk-20.11 works fine. > > - Upon comparing the working scenario and non-working scenario on esx > host, I > > could notice that there is some difference in port configuration of > vswitch. > > > > Below is the snapshot of working case, where the ethFRP:frame routing = { > > requested:filter flags is 0x1d. > > > > port { > > port index:365 > > vnic index:0x00000003 > > portCfg:build_1_15_2_vm-v3--p1e3-u2e3 > > dvPortId: > > clientName:sjc-cms-esx15-csm02-pan1 > > clientType: 5 -> VMM Virtual NIC > > clientSubType: 9 -> Vmxnet3 Client > > world leader:2120158 > > flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED > > Impl customized blocked flags:0x00000000 > > Passthru status: 0x8 -> DISABLED_BY_HOST > > fixed Hw Id:00:50:56:b8:20:aa: > > ethFRP:frame routing { > > requested:filter { > > flags:0x0000001d > > unicastAddr:00:50:56:b8:20:aa: > > numMulticastAddresses:0 > > multicastAddresses: > > LADRF:[0]: 0x0 > > [1]: 0x0 > > } > > accepted:filter { > > flags:0x0000001d > > unicastAddr:00:50:56:b8:20:aa: > > numMulticastAddresses:0 > > multicastAddresses: > > LADRF:[0]: 0x0 > > [1]: 0x0 > > } > > } > > > > > > For the non-working case the flag is set to 0x09. > > > > port { > > port index:365 > > vnic index:0x00000003 > > portCfg:build_1_15_2_vm-v3--p1e3-u2e3 > > dvPortId: > > clientName:sjc-cms-esx15-csm02-pan1 > > clientType: 5 -> VMM Virtual NIC > > clientSubType: 9 -> Vmxnet3 Client > > world leader:2120158 > > flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED > > Impl customized blocked flags:0x00000000 > > Passthru status: 0x8 -> DISABLED_BY_HOST > > fixed Hw Id:00:50:56:b8:20:aa: > > ethFRP:frame routing { > > requested:filter { > > flags:0x00000009 > > unicastAddr:00:50:56:b8:20:aa: > > numMulticastAddresses:0 > > multicastAddresses: > > LADRF:[0]: 0x0 > > [1]: 0x0 > > } > > accepted:filter { > > flags:0x00000009 > > unicastAddr:00:50:56:b8:20:aa: > > numMulticastAddresses:0 > > multicastAddresses: > > LADRF:[0]: 0x0 > > [1]: 0x0 > > } > > } > > filter supported features: 0 -> NONE > > filter properties: 0 -> NONE > > rx mode: 0 -> INLINE > > tune mode: 0 -> default > > fastpath switch ID:0xffffffff > > fastpath port ID:0xffffffff > > } > > > > I think these are some of the flags set by vmxnet3 device and in > dpdk-22.11, > > its not updating the flags. > > As a maintainer of the net/vmxnet3 driver, could you please register > to bugzilla? > And please have a look. > > > Thanks! > > -- > David marchand > > --00000000000053c22a05f86b1c99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jochen,=C2=A0

Could you please help here?

<= div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif">Regard= s
Amiya

On Fri, Mar 31, 2023 at 1:10=E2=80=AFPM David Marchand <david.marchand@redhat.com>= wrote:
Hello Jo= chen,

On Fri, Mar 31, 2023 at 9:07=E2=80=AFAM <bugzilla@dpdk.org> wrote:
>
> Bug ID 1209
> Summary vmxnet3 interface not receiving any packets with dpdk-22.11.1<= br> > Product DPDK
> Version 22.11
> Hardware x86
> OS All
> Status UNCONFIRMED
> Severity critical
> Priority Normal
> Component ethdev
> Assignee dev@dpdk.or= g
> Reporter amohakud@paloaltonetworks.com
> Target Milestone ---
>
> Hi,
> I recently upgraded our DPDK to 22.11.1 and observed that the guest vm= xnet3
> interface is not receiving any unicast packets. It's able to recei= ve the
> broadcast packets though. We enable promiscuous and all-multicast on t= he port.
>
> rte_eth_promiscuous_enable(port);
> rte_eth_allmulticast_enable(port);
>
> This happens when the vswitch has only 2 ports attached.
>
> On further triaging,
> -=C2=A0 I could find out that on the same setup, dpdk-20.11 works fine= .
> -=C2=A0 Upon comparing the working scenario and non-working scenario o= n esx host, I
> could notice that there is some difference in port configuration of vs= witch.
>
> Below is the snapshot of working case, where the=C2=A0 ethFRP:frame ro= uting {
> requested:filter flags is 0x1d.
>
> port {
>=C2=A0 =C2=A0 port index:365
>=C2=A0 =C2=A0 vnic index:0x00000003
>=C2=A0 =C2=A0 portCfg:build_1_15_2_vm-v3--p1e3-u2e3
>=C2=A0 =C2=A0 dvPortId:
>=C2=A0 =C2=A0 clientName:sjc-cms-esx15-csm02-pan1
>=C2=A0 =C2=A0 clientType: 5 -> VMM Virtual NIC
>=C2=A0 =C2=A0 clientSubType: 9 -> Vmxnet3 Client
>=C2=A0 =C2=A0 world leader:2120158
>=C2=A0 =C2=A0 flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED=
>=C2=A0 =C2=A0 Impl customized blocked flags:0x00000000
>=C2=A0 =C2=A0 Passthru status: 0x8 -> DISABLED_BY_HOST
>=C2=A0 =C2=A0 fixed Hw Id:00:50:56:b8:20:aa:
>=C2=A0 =C2=A0 ethFRP:frame routing {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0requested:filter {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 flags:0x0000001d
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 unicastAddr:00:50:56:b8:20:aa:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 numMulticastAddresses:0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 multicastAddresses:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LADRF:[0]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0}
>=C2=A0 =C2=A0 =C2=A0 =C2=A0accepted:filter {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 flags:0x0000001d
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 unicastAddr:00:50:56:b8:20:aa:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 numMulticastAddresses:0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 multicastAddresses:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LADRF:[0]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0}
>=C2=A0 =C2=A0 }
>
>
> For the non-working case the flag is set to 0x09.
>
> port {
>=C2=A0 =C2=A0 port index:365
>=C2=A0 =C2=A0 vnic index:0x00000003
>=C2=A0 =C2=A0 portCfg:build_1_15_2_vm-v3--p1e3-u2e3
>=C2=A0 =C2=A0 dvPortId:
>=C2=A0 =C2=A0 clientName:sjc-cms-esx15-csm02-pan1
>=C2=A0 =C2=A0 clientType: 5 -> VMM Virtual NIC
>=C2=A0 =C2=A0 clientSubType: 9 -> Vmxnet3 Client
>=C2=A0 =C2=A0 world leader:2120158
>=C2=A0 =C2=A0 flags: 0x40013 -> IN_USE ENABLED WORLD_ASSOC CONNECTED=
>=C2=A0 =C2=A0 Impl customized blocked flags:0x00000000
>=C2=A0 =C2=A0 Passthru status: 0x8 -> DISABLED_BY_HOST
>=C2=A0 =C2=A0 fixed Hw Id:00:50:56:b8:20:aa:
>=C2=A0 =C2=A0 ethFRP:frame routing {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0requested:filter {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 flags:0x00000009
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 unicastAddr:00:50:56:b8:20:aa:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 numMulticastAddresses:0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 multicastAddresses:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LADRF:[0]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0}
>=C2=A0 =C2=A0 =C2=A0 =C2=A0accepted:filter {
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 flags:0x00000009
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 unicastAddr:00:50:56:b8:20:aa:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 numMulticastAddresses:0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 multicastAddresses:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LADRF:[0]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1]: 0x0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0}
>=C2=A0 =C2=A0 }
>=C2=A0 =C2=A0 filter supported features: 0 -> NONE
>=C2=A0 =C2=A0 filter properties: 0 -> NONE
>=C2=A0 =C2=A0 rx mode: 0 -> INLINE
>=C2=A0 =C2=A0 tune mode: 0 -> default
>=C2=A0 =C2=A0 fastpath switch ID:0xffffffff
>=C2=A0 =C2=A0 fastpath port ID:0xffffffff
> }
>
> I think these are some of the flags set by vmxnet3 device and in dpdk-= 22.11,
> its not updating the flags.

As a maintainer of the net/vmxnet3 driver, could you please register
to bugzilla?
And please have a look.


Thanks!

--
David marchand

--00000000000053c22a05f86b1c99--