From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
Cc: Yongseok Koh <yskoh@mellanox.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix flow director matching rules
Date: Mon, 30 Oct 2017 17:53:11 -0700 [thread overview]
Message-ID: <3942429a-2bff-e3e9-a969-ddf5625d3a52@intel.com> (raw)
In-Reply-To: <f2bec253721344d85a2d510019aeff78aa55bdc4.1509086974.git.nelio.laranjeiro@6wind.com>
On 10/26/2017 11:50 PM, Nelio Laranjeiro wrote:
> Flow director API does not provide a layer 2 configuration when the filter
> is for layer 3 and 4 causing the translation to generic flow API to be
> wrong, as not providing a mask for layer ends by using the default one. In
> this case, the Ethernet mask layer is full whereas it must be empty.
>
> Fixes: 4c3e9bcdd52e ("net/mlx5: support flow director")
>
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-10-31 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 6:50 Nelio Laranjeiro
2017-10-31 0:53 ` Ferruh Yigit [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=3942429a-2bff-e3e9-a969-ddf5625d3a52@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--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).