DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>
Cc: Matan Azrad <matan@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>, dev <dev@dpdk.org>,
	Ori Kam <orika@mellanox.com>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx4: fix default flow rule create
Date: Wed, 27 Feb 2019 02:56:33 +0000	[thread overview]
Message-ID: <3FDA1FB6-5EED-46BC-8571-E810964CE8FB@mellanox.com> (raw)
In-Reply-To: <1551001269-62890-1-git-send-email-dekelp@mellanox.com>


> On Feb 24, 2019, at 1:41 AM, Dekel Peled <dekelp@mellanox.com> wrote:
> 
> Original patch changed logic of function mlx4_flow_merge_eth().
> The setting of flow->promisc was wrongly removed.
> This patch adds the removed setting of flow->promisc, to restore
> the required behavior.
> 
> Fixes: c0d239263156 ("net/mlx4: support flow w/o ETH spec and with VLAN")
> Cc: stable@dpdk.org
> 
> ---
> v2: Correct typo in 'stable' email address.
> ---
> 
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> ---

Acked-by: Yongseok Koh <yskoh@mellanox.com>
 
Thanks

> drivers/net/mlx4/mlx4_flow.c | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/mlx4/mlx4_flow.c b/drivers/net/mlx4/mlx4_flow.c
> index 3abde30..b7af324 100644
> --- a/drivers/net/mlx4/mlx4_flow.c
> +++ b/drivers/net/mlx4/mlx4_flow.c
> @@ -250,6 +250,7 @@ struct mlx4_drop {
> 	if (!mask) {
> 		eth->val.dst_mac[0] = 0xff;
> 		flow->ibv_attr->type = IBV_FLOW_ATTR_ALL_DEFAULT;
> +		flow->promisc = 1;
> 		return 0;
> 	}
> 	memcpy(eth->val.dst_mac, spec->dst.addr_bytes, ETHER_ADDR_LEN);
> -- 
> 1.8.3.1
> 

  reply	other threads:[~2019-02-27  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24  8:07 [dpdk-dev] [PATCH] " Dekel Peled
2019-02-24  9:41 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2019-02-27  2:56   ` Yongseok Koh [this message]
2019-03-07  8:35     ` Shahaf Shuler

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=3FDA1FB6-5EED-46BC-8571-E810964CE8FB@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@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).