From: Simon Horman <simon.horman@corigine.com>
To: Saeed Mahameed <saeed@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Mark Bloch <mbloch@nvidia.com>, Shay Drory <shayd@nvidia.com>,
Roi Dayan <roid@nvidia.com>
Subject: Re: [net-next 03/14] net/mlx5e: rep, store send to vport rules per peer
Date: Fri, 2 Jun 2023 18:02:30 +0200 [thread overview]
Message-ID: <ZHoSlnSX0K4xeZOF@corigine.com> (raw)
In-Reply-To: <20230601060118.154015-4-saeed@kernel.org>
On Wed, May 31, 2023 at 11:01:07PM -0700, Saeed Mahameed wrote:
> From: Mark Bloch <mbloch@nvidia.com>
>
> Each representor, for each send queue, is holding a
> send_to_vport rule for the peer eswitch.
>
> In order to support more than one peer, and to map between the peer
> rules and peer eswitches, refactor representor to hold both the peer
> rules and pointer to the peer eswitches.
> This enables mlx5 to store send_to_vport rules per peer, where each
> peer have dedicate index via mlx5_get_dev_index().
>
> Signed-off-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Shay Drory <shayd@nvidia.com>
> Reviewed-by: Roi Dayan <roid@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
...
> @@ -426,15 +437,24 @@ static int mlx5e_sqs2vport_start(struct mlx5_eswitch *esw,
> rep_sq->sqn = sqns_array[i];
>
> if (peer_esw) {
> + int peer_rule_idx = mlx5_get_dev_index(peer_esw->dev);
> +
> + sq_peer = kzalloc(sizeof(*sq_peer), GFP_KERNEL);
> + if (!sq_peer)
> + goto out_sq_peer_err;
Hi Mark and Saeed,
Jumping to out_sq_peer_err will return err.
But err seems to be uninitialised here.
> +
> flow_rule = mlx5_eswitch_add_send_to_vport_rule(peer_esw, esw,
> rep, sqns_array[i]);
> if (IS_ERR(flow_rule)) {
> err = PTR_ERR(flow_rule);
> - mlx5_eswitch_del_send_to_vport_rule(rep_sq->send_to_vport_rule);
> - kfree(rep_sq);
> - goto out_err;
> + goto out_flow_rule_err;
> }
> - rep_sq->send_to_vport_rule_peer = flow_rule;
> +
> + sq_peer->rule = flow_rule;
> + sq_peer->peer = peer_esw;
> + err = xa_insert(&rep_sq->sq_peer, peer_rule_idx, sq_peer, GFP_KERNEL);
> + if (err)
> + goto out_xa_err;
> }
>
> list_add(&rep_sq->list, &rpriv->vport_sqs_list);
> @@ -445,6 +465,14 @@ static int mlx5e_sqs2vport_start(struct mlx5_eswitch *esw,
>
> return 0;
>
> +out_xa_err:
> + mlx5_eswitch_del_send_to_vport_rule(flow_rule);
> +out_flow_rule_err:
> + kfree(sq_peer);
> +out_sq_peer_err:
> + mlx5_eswitch_del_send_to_vport_rule(rep_sq->send_to_vport_rule);
> + xa_destroy(&rep_sq->sq_peer);
> + kfree(rep_sq);
> out_err:
> mlx5e_sqs2vport_stop(esw, rep);
>
...
next prev parent reply other threads:[~2023-06-02 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 6:01 [pull request][net-next 00/14] mlx5 updates 2023-05-31 Saeed Mahameed
2023-06-01 6:01 ` [net-next 01/14] net/mlx5e: en_tc, Extend peer flows to a list Saeed Mahameed
2023-06-01 6:01 ` [net-next 02/14] net/mlx5e: tc, Refactor peer add/del flow Saeed Mahameed
2023-06-01 6:01 ` [net-next 03/14] net/mlx5e: rep, store send to vport rules per peer Saeed Mahameed
2023-06-02 16:02 ` Simon Horman [this message]
2023-06-02 18:46 ` Saeed Mahameed
2023-06-03 7:25 ` Simon Horman
2023-06-01 6:01 ` [net-next 04/14] net/mlx5e: en_tc, re-factor query route port Saeed Mahameed
2023-06-01 6:01 ` [net-next 05/14] net/mlx5e: Handle offloads flows per peer Saeed Mahameed
2023-06-01 6:01 ` [net-next 06/14] net/mlx5: E-switch, enlarge peer miss group table Saeed Mahameed
2023-06-01 6:01 ` [net-next 07/14] net/mlx5: E-switch, refactor FDB miss rule add/remove Saeed Mahameed
2023-06-01 6:01 ` [net-next 08/14] net/mlx5: E-switch, Handle multiple master egress rules Saeed Mahameed
2023-06-01 6:01 ` [net-next 09/14] net/mlx5: E-switch, generalize shared FDB creation Saeed Mahameed
2023-06-01 6:01 ` [net-next 10/14] net/mlx5: DR, handle more than one peer domain Saeed Mahameed
2023-06-01 6:01 ` [net-next 11/14] net/mlx5: Devcom, Rename paired to ready Saeed Mahameed
2023-06-01 6:01 ` [net-next 12/14] net/mlx5: E-switch, mark devcom as not ready when all eswitches are unpaired Saeed Mahameed
2023-06-01 6:01 ` [net-next 13/14] net/mlx5: Devcom, introduce devcom_for_each_peer_entry Saeed Mahameed
2023-06-01 6:01 ` [net-next 14/14] net/mlx5: Devcom, extend mlx5_devcom_send_event to work with more than two devices 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=ZHoSlnSX0K4xeZOF@corigine.com \
--to=simon.horman@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.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).