From: madhukar mythri <madhukar.mythri@gmail.com>
To: users <users@dpdk.org>
Subject: IPv6 Multicast packets not received by the DPDK primary process (with MLX5 device)
Date: Tue, 13 Sep 2022 11:58:36 +0530 [thread overview]
Message-ID: <CAAUNki1-vq_dbHC31byeuqh8Q1NjPstNt70ZQHEBNx4E8MFeag@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]
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:
==================================
• IPv6 Multicast messages are not supported on VM, while promiscuous 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.
==================================
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.
[-- Attachment #2: Type: text/html, Size: 2237 bytes --]
reply other threads:[~2022-09-13 6:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAUNki1-vq_dbHC31byeuqh8Q1NjPstNt70ZQHEBNx4E8MFeag@mail.gmail.com \
--to=madhukar.mythri@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).