From: Thomas Monjalon <thomas@monjalon.net>
To: Liwu Liu <liwuliu@fortinet.com>
Cc: users@dpdk.org, erezf@mellanox.com, kiranv@mellanox.com,
rasland@mellanox.com, asafp@mellanox.com
Subject: Re: [dpdk-users] mlx5 PMD fails to receive certain icmpv6 multicast
Date: Thu, 07 May 2020 00:05:26 +0200 [thread overview]
Message-ID: <3620277.fW5hKsROvD@thomas> (raw)
In-Reply-To: <1753687.1xdlsreqCQ@xps>
26/03/2020 22:11, Thomas Monjalon:
> 06/03/2020 01:45, Liwu Liu:
> > Hi Team,
> >
> > I am using the mlx5/100G in KVM guest. The host shows this PCI vfNIC is provisioned to the guest:
> > "17:01.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5 Virtual Function]"
> >
> > I am using DPDK 19.11 with kind of standard configurations, and when DPDK application runs I still have the kernel mlx5e net device present. I have both promiscuous and all-multicast turned on.
> >
> > It works fine for IPV4, but for IPV6 it fails. It can receive packets destined to 33:33:00:00:00:02 (IPV6 Router solicitation), but cannot receive packets destined to 33:33:ff:00:00:01 (IPV6 neighbor solicitation for some address).
> >
> > But if I avoid DPDK, directly use the OFED-4.6 based kernel driver, everything works fine as expected.
> >
> > I am thinking there is some mismatch happened for MLX5 PMD. Please give some advice/hints.
>
> Adding Mellanox engineers in Cc list for help.
Any update to share please?
next prev parent reply other threads:[~2020-05-06 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 0:45 Liwu Liu
2020-03-26 21:11 ` Thomas Monjalon
2020-05-06 22:05 ` Thomas Monjalon [this message]
2020-05-06 22:38 ` Liwu Liu
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=3620277.fW5hKsROvD@thomas \
--to=thomas@monjalon.net \
--cc=asafp@mellanox.com \
--cc=erezf@mellanox.com \
--cc=kiranv@mellanox.com \
--cc=liwuliu@fortinet.com \
--cc=rasland@mellanox.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).