netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@mellanox.com>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Eli Britstein <elibr@mellanox.com>
Subject: Re: [PATCH mlx5-next 08/10] net/mlx5: Support extended destination format in flow steering command
Date: Mon, 10 Dec 2018 16:16:20 +0000	[thread overview]
Message-ID: <20181210161614.GG3459@mellanox.com> (raw)
In-Reply-To: <20181210030442.7543-9-saeedm@mellanox.com>

On Sun, Dec 09, 2018 at 07:04:40PM -0800, Saeed Mahameed wrote:
> From: Eli Britstein <elibr@mellanox.com>
> 
> Update the flow steering command formatting according to the extended
> destination API.
> Note that the FW dictates that multi destination FTEs that involve at
> least one encap must use the extended destination format, while single
> destination ones must use the legacy format.
> Using extended destination format requires FW support. Check for its
> capabilities and return error if not supported.
> 
> Signed-off-by: Eli Britstein <elibr@mellanox.com>
> Reviewed-by: Or Gerlitz <ogerlitz@mellanox.com>
> Reviewed-by: Oz Shlomo <ozsh@mellanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
>  .../net/ethernet/mellanox/mlx5/core/fs_cmd.c  | 80 +++++++++++++++++--
>  include/linux/mlx5/fs.h                       |  2 +
>  2 files changed, 75 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c b/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c
> index dda63dedaa49..a18fbea7a931 100644
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c
> @@ -308,22 +308,68 @@ static int mlx5_cmd_destroy_flow_group(struct mlx5_core_dev *dev,
>  	return mlx5_cmd_exec(dev, in, sizeof(in), out, sizeof(out));
>  }
>  
> +static int mlx5_set_extended_dest(struct mlx5_core_dev *dev,
> +				  struct fs_fte *fte, bool *extended_dest)
> +{
> +	int fw_log_max_fdb_encap_uplink =
> +		MLX5_CAP_ESW(dev, log_max_fdb_encap_uplink);
> +	int num_fwd_destinations = 0;
> +	struct mlx5_flow_rule *dst;
> +	int num_encap = 0;
> +
> +	*extended_dest = false;
> +	if (!(fte->action.action & MLX5_FLOW_CONTEXT_ACTION_FWD_DEST))
> +		return 0;
> +
> +	list_for_each_entry(dst, &fte->node.children, node.list) {
> +		if (dst->dest_attr.type == MLX5_FLOW_DESTINATION_TYPE_COUNTER)
> +			continue;
> +		if (dst->dest_attr.type == MLX5_FLOW_DESTINATION_TYPE_VPORT &&
> +		    dst->dest_attr.vport.flags & MLX5_FLOW_DEST_VPORT_REFORMAT_ID)
> +			num_encap++;
> +		num_fwd_destinations++;
> +	}
> +	if (num_fwd_destinations > 1 && num_encap > 0)
> +		*extended_dest = true;
> +
> +	if (*extended_dest && !fw_log_max_fdb_encap_uplink) {
> +		pr_warn("FW does not support extended destination");
> +		return -EOPNOTSUPP;
> +	}
> +	if (num_encap > (1 << fw_log_max_fdb_encap_uplink)) {
> +		pr_warn("FW does not support more than %d encaps",
> +			1 << fw_log_max_fdb_encap_uplink);

Drivers should avoid using pr_ if they have an struct device, in this
case &dev->pdev->dev ..

This is probably a comment for the entire core code directory I
suppose?

Jason

  reply	other threads:[~2018-12-10 16:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10  3:04 [PATCH mlx5-next 00/10] mlx5 core updates and cleanups Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 01/10] net/mlx5: Rework handling of port module events Saeed Mahameed
2018-12-10 16:09   ` Jason Gunthorpe
2018-12-10 19:07     ` Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 02/10] net/mlx5: Add support for PCIe power slot exceeded error in PME Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 03/10] net/mlx5: Add support for plugged-disabled cable status " Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 04/10] net/mlx5: Add monitor commands layout and event data Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 05/10] net/mlx5: Revise gre and nvgre key formats Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 06/10] net/mlx5: Introduce extended destination fields Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 07/10] net/mlx5: E-Switch, Change vhca id valid bool field to bit flag Saeed Mahameed
2018-12-10 16:12   ` Jason Gunthorpe
2018-12-10 19:12     ` Saeed Mahameed
2018-12-10 21:05       ` Or Gerlitz
2018-12-10 21:18         ` Saeed Mahameed
2018-12-10 19:51     ` Or Gerlitz
2018-12-10  3:04 ` [PATCH mlx5-next 08/10] net/mlx5: Support extended destination format in flow steering command Saeed Mahameed
2018-12-10 16:16   ` Jason Gunthorpe [this message]
2018-12-10 19:13     ` Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 09/10] IB/mlx5: Simplify netdev unbinding Saeed Mahameed
2018-12-10  3:04 ` [PATCH mlx5-next 10/10] net/mlx5: Remove the get protocol device interface entry Saeed Mahameed

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=20181210161614.GG3459@mellanox.com \
    --to=jgg@mellanox.com \
    --cc=elibr@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@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).