From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Richard Nutman <Richard.Nutman@s-a-m.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Yongseok Koh <yskoh@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-users] Requiring rte_eth_allmulticast_enable in 18.02.1
Date: Thu, 3 May 2018 15:23:05 +0200 [thread overview]
Message-ID: <20180503132305.4iuuxgff5bfphxqm@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <733AB18813E3864094592CC5191B172A235BD9F9@EX-UKHA-01.ad.s-a-m.com>
Hi Richard,
On Thu, May 03, 2018 at 09:59:00AM +0000, Richard Nutman wrote:
> Hi all,
>
> I managed to get 18.02.1 building and working for Mellanox MLX5 PMD.
>
> I am using the Flow Director still, and previously with Mellanox
> 16.11_4.0 I had no problem receiving multicast packets.
Not really easy to understand what you are talking about as this DPDK
you mention is a not released by DPDK community. How can we know what
is present in this code?
> With 18.02.1 I am forced to use rte_eth_allmulticast_enable to see
> multicast packets on the receive side.
>
> Question: Is this expected, or should I be just adding the MAC address
> of the flow into the whitelist ?
>
> I assume the old Flow Director code was doing this before, but somehow
> it looks like it's stopped doing this, perhaps in being switched over
> to use the new rte_flow underneath ?
>
> Is rte_eth_allmulticast_enable, or adding the MAC addresses to
> whitelist required, or expected to be used with the new rte_flow ?
The old FDIR was converted to Verbs flows, new implementation of FDIR is
converted to rte_flow flow and then converted to Verb flows.
You should have the same behavior, unless there is something done by the
Mellanox DPDK bundle you were using until now.
Can you test with an official DPDK 16.11 [1] ?
Regards,
[1] https://fast.dpdk.org/rel/dpdk-16.04.tar.xz
--
Nélio Laranjeiro
6WIND
prev parent reply other threads:[~2018-05-03 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 9:59 Richard Nutman
2018-05-03 13:23 ` Nélio Laranjeiro [this message]
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=20180503132305.4iuuxgff5bfphxqm@laranjeiro-vm.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=Richard.Nutman@s-a-m.com \
--cc=adrien.mazarguil@6wind.com \
--cc=shahafs@mellanox.com \
--cc=users@dpdk.org \
--cc=yskoh@mellanox.com \
/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).