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 E48FEA0032 for ; Tue, 13 Sep 2022 08:28:47 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 764DA40156; Tue, 13 Sep 2022 08:28:47 +0200 (CEST) Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) by mails.dpdk.org (Postfix) with ESMTP id 7880340151 for ; Tue, 13 Sep 2022 08:28:46 +0200 (CEST) Received: by mail-io1-f48.google.com with SMTP id v128so8772915ioe.12 for ; Mon, 12 Sep 2022 23:28:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date; bh=vUyvVW+4QepyO6AAkU2Xup7XsSIAF2/vR6Op6/T7LE0=; b=Gc0LZLnj0/C6uJxb99rkUH1ltMVREuhqiGaD+nNE2Fz6IeP54C6myyFkDmpXMYXJYn soPiz9UjXlTRCGrSijfFrFZkF5Zi+9DvneSZBqh6FHboY31FjNicmvqoGLeJEn0NDsKp EuCMFM+mZIaGl/eOvNM7Wq1s16NmDpb9kjxIKUyZ8y4eIxIX6hy3fWUFw21136FyDJFV 2x9cZSpS1x/mKZ5tKnbAoqTxP1xyKwNK5QJnFjeY38qwIPWcibbEqeG7HEAHQGVd9XZ2 brTrHi2PRCl1HYmt/ZlJuSO4LKIdI19oCTRXBSIJLMuX0NellSRo2WhErhZSdUBp5I5u hhxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date; bh=vUyvVW+4QepyO6AAkU2Xup7XsSIAF2/vR6Op6/T7LE0=; b=YPddHnaYuUr7DP+5XGsDQCLPtIwsgFUZPd5GN1yY8RkDV6PWGs4uM8sC9uWc1HJ1gw 7FFhBjSS7qHeW75isqUn75+29kt5X1e5foolmQwebT2stimMAF3yz289zpesc2VHyy6f EihbP4o4IWjhj7OA6rXM4ZZ+LN/gV2RvcqwU3qCt/+NM0JnsypmuCr259nCcYGSepWM7 TGQs3iS9y5SrjhVB7BgPFHDtvqxMNLXbekV8mH3mrgPN1WG7DXHXaPVmBZSlqJWwP6Z4 TBUac48MTEUoZ81BIIIkdLGxLqVTAvPooJe68GNEa8pnN82bPLb4LGNaW5VMHdy/JX9O /Sqg== X-Gm-Message-State: ACgBeo2eLuhLib0ObdeFj7LbbLaGF8q4QqTnW4WDw6lgO4Q5+wkiw9tj HG+sJ7eOLFOiI/YlqWen3hT9iolk3HBrwKTTpEHXQ2NKdpQ= X-Google-Smtp-Source: AA6agR6UzUSeDhtAz3LZybNscygrhxUfzMYFuKINuJMPKr9XNKEIsLeREsLCXEwU1G8xS22/FUngHeY+TBTryZzozq8= X-Received: by 2002:a05:6638:40a3:b0:35a:3f2d:a21c with SMTP id m35-20020a05663840a300b0035a3f2da21cmr3811057jam.221.1663050525388; Mon, 12 Sep 2022 23:28:45 -0700 (PDT) MIME-Version: 1.0 From: madhukar mythri Date: Tue, 13 Sep 2022 11:58:36 +0530 Message-ID: Subject: IPv6 Multicast packets not received by the DPDK primary process (with MLX5 device) To: users Content-Type: multipart/alternative; boundary="000000000000cf331705e8891fae" 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 --000000000000cf331705e8891fae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On our DPDK primary application (based of MLX5 PMD/Device), facing issue in receiving the IPv6 "Neighbor-Solicitation" packets which is based on Multi-cast address. Our DPDK primrary application is configured in Flow-isolation mode, by adding the Unicast, Multi-cast and Broad-cast MAC address flows using the rte_flow_create() API, such that we are able to receive all type(IPv6 and IPv4) of packets were received well, except the Multi-cast address packet on the secondary IP-address which is not configured as part of Linux Kernel netDevice interface. Multi-cast packets were received well only which we add the IP-address on the Linux Kernel interface(ethX based of mlx5_core driver interface) and if we do not add the IP-address on Linux kernel interface then the IPv6 "Neighbor-Solicitation" Multi-cast packet was not received to the DPDK primary application. We found a limitation on DPDK MLX5 PMD guide w.r.t IPv6 Multi-cast packets in the following URL: https://doc.dpdk.org/guides/nics/mlx5.html , as follows: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D =E2=80=A2 IPv6 Multicast messages are not supported on VM, while promiscuou= s mode and allmulticast mode are both set to off. To receive IPv6 Multicast messages on VM, explicitly set the relevant MAC address using rte_eth_dev_mac_addr_add() API. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D But, when we enable the Promiscuous and All-Multicast mode, DPDK mlx5 PMD return Error saying "cannot enable in Flow-isolation mode". So, does this IPv6 Multicast limitation still exist ? if so, please let us know, what is the work-around on this ? DPDK-version: DPDK-21.11. Linux kernel driver and firmware-version details: ~ # ethtool -i eth1 driver: mlx5_core version: 5.0-0 firmware-version: 14.23.1020 (MT_2420110004) expansion-rom-version: bus-info: 0000:00:08.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes ~ # Thanks, Madhukar. --000000000000cf331705e8891fae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

On our DPDK primary application (ba= sed of MLX5 PMD/Device), facing issue in receiving the IPv6 "Neighbor-= Solicitation" packets which is based on Multi-cast address.
Our DPD= K primrary application is configured in Flow-isolation mode, by adding the = Unicast, Multi-cast and Broad-cast MAC address flows using the rte_flow_cre= ate() API, such that we are able to receive all type(IPv6 and IPv4) of pack= ets were received well, except the Multi-cast address packet on the seconda= ry IP-address which is not configured as part of Linux Kernel netDevice int= erface.

Multi-cast packets were received well only which we add the = IP-address on the Linux Kernel interface(ethX based of mlx5_core driver int= erface) and if we do not add the IP-address on Linux kernel interface then = the IPv6 "Neighbor-Solicitation" Multi-cast packet was not receiv= ed to the DPDK primary application.

We found a limitation on DPDK ML= X5 PMD guide w.r.t IPv6 Multi-cast packets in the following URL: https://doc.dpdk.org/guides/ni= cs/mlx5.html , as follows:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
= =E2=80=A2 IPv6 Multicast messages are not supported on VM, while promiscuou= s mode and allmulticast mode are both set to off. To receive IPv6 Multicast= messages on VM, explicitly set the relevant MAC address using rte_eth_dev_= mac_addr_add() API.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=C2=A0 =C2=A0
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 But, when we enable the Promiscuous and All-Mul= ticast mode, DPDK mlx5 PMD return Error saying "cannot enable in Flow-= isolation mode".

So, does this IPv6 Multicast limitation stil= l exist ?=C2=A0=C2=A0if so, please let us know, what is the work-around on = this ?

DPDK-version: DPDK-21.11.

Linux kernel driver and firm= ware-version details:
~ # ethtool -i eth1 =C2=A0
driver: mlx5_coreversion: 5.0-0
firmware-version: 14.23.1020 (MT_2420110004)
expansi= on-rom-version:
bus-info: 0000:00:08.0
supports-statistics: yes
su= pports-test: yes
supports-eeprom-access: no
supports-register-dump: n= o
supports-priv-flags: yes
~ #

Thanks,
Madhukar.
--000000000000cf331705e8891fae--