[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMhuZeRakGubqiZzQRwdhRYLgLzQwOCS6MdxBOujViKXJA@mail.gmail.com>
Date: Mon, 27 Jun 2016 23:40:07 +0300
From: Or Gerlitz <gerlitz.or@...il.com>
To: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc: Saeed Mahameed <saeedm@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
Hadar Hen-Zion <hadarh@...lanox.com>,
Jiri Pirko <jiri@...lanox.com>,
Andy Gospodarek <gospo@...ulusnetworks.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
John Fastabend <john.r.fastabend@...el.com>
Subject: Re: [PATCH net-next 03/16] net/mlx5: E-Switch, Add miss rule for
offloads mode
On Mon, Jun 27, 2016 at 7:53 PM, Sergei Shtylyov
<sergei.shtylyov@...entembedded.com> wrote:
>> +static int esw_add_fdb_miss_rule(struct mlx5_eswitch *esw)
>> +{
>> + struct mlx5_flow_destination dest;
>> + struct mlx5_flow_rule *flow_rule = NULL;
>> + int match_header = 0;
>
>
> This variable doesn't appear necessary...
yep
>> + dest.type = MLX5_FLOW_DESTINATION_TYPE_VPORT;
>> + dest.vport_num = 0;
>> +
>> + flow_rule = mlx5_add_flow_rule(esw->fdb_table.fdb, match_header,
>> match_c,
>
>
> Why not just pass 0 instead of 'match_header'?
Correct, will fix that.
Powered by blists - more mailing lists