From: Amir Vadai <amir@vadai.me>
To: Saeed Mahameed <saeedm@dev.mellanox.co.il>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>,
John Fastabend <john.r.fastabend@intel.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Hadar Har-Zion <hadarh@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>
Subject: Re: [PATCH net-next 6/8] net/mlx5e: Introduce tc offload support
Date: Tue, 1 Mar 2016 19:07:42 +0200 [thread overview]
Message-ID: <20160301170742.GA26373@office.Home> (raw)
In-Reply-To: <CALzJLG8oPTwoowafcPODKwZ4=Uxeqs2jqr6L7UUME_ZVmx66wg@mail.gmail.com>
On Tue, Mar 01, 2016 at 05:59:59PM +0200, Saeed Mahameed wrote:
> On Tue, Mar 1, 2016 at 4:24 PM, Amir Vadai <amir@vadai.me> wrote:
> > +#define FT_CAP(f) MLX5_CAP_FLOWTABLE(mdev, flow_table_properties_nic_receive.f)
> > + if (FT_CAP(flow_modify_en) &&
> > + FT_CAP(modify_root) &&
> > + FT_CAP(identified_miss_table_mode) &&
> > + FT_CAP(flow_table_modify))
> > + priv->netdev->hw_features |= NETIF_F_HW_TC;
> > +
> > netdev->features |= NETIF_F_HIGHDMA;
> >
> > netdev->priv_flags |= IFF_UNICAST_FLT;
> >
> > + mlx5e_tc_init(priv);
>
> This is not the place for this, We usually do internal data structure
> initialization after we create all HW resources in
> mlx5e_create_netdev
> Please see mlx5e_vxlan_init as example, and you already call
> mlx5e_tc_cleanup inside mlx5e_destroy_netdev, please move the
> mlx5e_tc_init
> to mlx5e_create_netdev after HW resources creation,
ack
>
>
> > @@ -2558,6 +2588,7 @@ static void mlx5e_destroy_netdev(struct mlx5_core_dev *mdev, void *vpriv)
> > mlx5_core_dealloc_transport_domain(priv->mdev, priv->tdn);
> > mlx5_core_dealloc_pd(priv->mdev, priv->pdn);
> > mlx5_unmap_free_uar(priv->mdev, &priv->cq_uar);
> > + mlx5e_tc_cleanup(priv);
>
> I would suggest to move mlx5e_tc_init to be right after
> mlx5e_vxlan_init and mlx5e_tc_cleanup before mlx5e_vxlan_cleanup.
ok
>
> > +struct mlx5_flow_rule *mlx5e_tc_add_flow(struct mlx5e_priv *priv,
> > + u32 *match_c, u32 *match_v,
> > + u32 action, u32 flow_tag)
> > +{
> > + struct mlx5_flow_destination dest = {
> > + .type = MLX5_FLOW_DESTINATION_TYPE_FLOW_TABLE,
> > + {.ft = priv->fts.vlan.t},
> > + };
> > + struct mlx5_flow_rule *rule;
> > + bool table_created = false;
> > +
> > + if (IS_ERR_OR_NULL(priv->fts.tc.t)) {
> > + priv->fts.tc.t =
> > + mlx5_create_auto_grouped_flow_table(priv->fts.ns, 0,
> > + MLX5E_TC_FLOW_TABLE_NUM_ENTRIES,
> > + MLX5E_TC_FLOW_TABLE_NUM_GROUPS);
> > + if (IS_ERR(priv->fts.tc.t)) {
> > + netdev_err(priv->netdev,
> > + "Failed to create tc offload table\n");
> > + return ERR_CAST(priv->fts.tc.t);
>
> Here priv->fts.tc.t will be invalid pointer and in your code you treat
> it as NULL in case of failure.
>
> > + }
> > +
> > + table_created = true;
> > + }
> > +
> > + rule = mlx5_add_flow_rule(priv->fts.tc.t, MLX5_MATCH_OUTER_HEADERS,
> > + match_c, match_v,
> > + action, flow_tag,
> > + action & MLX5_FLOW_CONTEXT_ACTION_FWD_DEST ? &dest : NULL);
> > +
> > + if (IS_ERR(rule) && table_created) {
> > + mlx5_destroy_flow_table(priv->fts.tc.t);
> > + priv->fts.tc.t = NULL;
> > + }
> > +
> > + return rule;
> > +}
> > +
>
> > +void mlx5e_tc_cleanup(struct mlx5e_priv *priv)
> > +{
> > + struct mlx5e_tc_flow_table *tc = &priv->fts.tc;
> > +
> > + rhashtable_free_and_destroy(&tc->ht, _mlx5e_tc_del_flow, priv);
> > +
> > + if (priv->fts.tc.t) {
>
> priv->fts.tc.t will be invalid pointer and this test will pass in case
> mlx5_create_auto_grouped_flow_table had failed
Yeh - should have used !IS_ERR_OR_NULL() or set it to NULL on failure
above.
Thanks,
Amir
>
> > + mlx5_destroy_flow_table(priv->fts.tc.t);
> > + priv->fts.tc.t = NULL;
> > + }
> > +}
next prev parent reply other threads:[~2016-03-01 17:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 14:24 [PATCH net-next 0/8] cls_flower hardware offload support Amir Vadai
2016-03-01 14:24 ` [PATCH net-next 1/8] net/flower: Introduce " Amir Vadai
2016-03-01 14:47 ` Jiri Pirko
2016-03-01 16:49 ` Amir Vadai
2016-03-01 17:01 ` Jiri Pirko
2016-03-02 11:14 ` Or Gerlitz
2016-03-02 13:22 ` Jiri Pirko
2016-03-02 16:22 ` John Fastabend
2016-03-02 16:30 ` Jiri Pirko
2016-03-01 14:53 ` Jiri Pirko
2016-03-01 16:50 ` Amir Vadai
2016-03-01 14:24 ` [PATCH net-next 2/8] net/flow_dissector: Make dissector_uses_key() and skb_flow_dissector_target() public Amir Vadai
2016-03-01 14:24 ` [PATCH net-next 3/8] net/act_skbedit: Utility functions for mark action Amir Vadai
2016-03-01 14:24 ` [PATCH net-next 4/8] net/mlx5_core: Set flow steering dest only for forward rules Amir Vadai
2016-03-01 14:24 ` [PATCH net-next 5/8] net/mlx5e: Add a new priority for kernel flow tables Amir Vadai
2016-03-01 14:24 ` [PATCH net-next 6/8] net/mlx5e: Introduce tc offload support Amir Vadai
2016-03-01 14:52 ` Jiri Pirko
2016-03-01 17:00 ` Amir Vadai
2016-03-01 17:13 ` John Fastabend
2016-03-02 15:53 ` Amir Vadai
2016-03-02 15:58 ` Jiri Pirko
2016-03-01 15:59 ` Saeed Mahameed
2016-03-01 17:07 ` Amir Vadai [this message]
2016-03-01 14:24 ` [PATCH net-next 7/8] net/mlx5e: Support offload cls_flower with drop action Amir Vadai
2016-03-01 14:55 ` Jiri Pirko
2016-03-01 16:50 ` Amir Vadai
2016-03-01 15:03 ` Jiri Pirko
2016-03-01 14:24 ` [PATCH net-next 8/8] net/mlx5e: Support offload cls_flower with sskbedit mark action Amir Vadai
2016-03-01 14:58 ` Jiri Pirko
2016-03-01 16:53 ` Amir Vadai
2016-03-01 17:18 ` [PATCH net-next 0/8] cls_flower hardware offload support John Fastabend
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=20160301170742.GA26373@office.Home \
--to=amir@vadai.me \
--cc=davem@davemloft.net \
--cc=hadarh@mellanox.com \
--cc=jiri@mellanox.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=saeedm@dev.mellanox.co.il \
--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).