From: Paolo Abeni <pabeni@redhat.com>
To: Hariprasad Kelam <hkelam@marvell.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
jerinj@marvell.com, sbhatta@marvell.com, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, saeedm@nvidia.com,
richardcochran@gmail.com, tariqt@nvidia.com,
linux-rdma@vger.kernel.org, maxtram95@gmail.com,
naveenm@marvell.com, hariprasad.netdev@gmail.com
Subject: Re: [net-next PATCH V3 4/4] octeontx2-pf: Add support for HTB offload
Date: Tue, 07 Feb 2023 13:48:11 +0100 [thread overview]
Message-ID: <b25f37e4e11d9da5b6d61cbfaa0cafe9889c3926.camel@redhat.com> (raw)
In-Reply-To: <20230206054640.5854-5-hkelam@marvell.com>
On Mon, 2023-02-06 at 11:16 +0530, Hariprasad Kelam wrote:
> +static int otx2_qos_txschq_alloc(struct otx2_nic *pfvf,
> + struct otx2_qos_cfg *cfg)
> +{
> + struct nix_txsch_alloc_req *req;
> + struct nix_txsch_alloc_rsp *rsp;
> + struct mbox *mbox = &pfvf->mbox;
> + int lvl, rc, schq;
> +
> + mutex_lock(&mbox->lock);
> + req = otx2_mbox_alloc_msg_nix_txsch_alloc(&pfvf->mbox);
> + if (!req)
> + return -ENOMEM;
This does not releases the mbox->lock mutex on error (another
occurrence below).
[...]
> +static int otx2_qos_txschq_update_config(struct otx2_nic *pfvf,
> + struct otx2_qos_node *node,
> + struct otx2_qos_cfg *cfg)
> +{
> + int ret = 0;
> +
> + otx2_qos_txschq_fill_cfg(pfvf, node, cfg);
> + ret = otx2_qos_txschq_push_cfg(pfvf, node, cfg);
> +
> + return ret;
I personally find the plain:
return <function>
more easy to read - more instances below.
[...]
> +static void otx2_reset_qdisc(struct net_device *dev, u16 qid)
> +{
> + struct netdev_queue *dev_queue = netdev_get_tx_queue(dev, qid);
> + struct Qdisc *qdisc = dev_queue->qdisc_sleeping;
> +
> + if (!qdisc)
> + return;
> +
> + spin_lock_bh(qdisc_lock(qdisc));
> + qdisc_reset(qdisc);
> + spin_unlock_bh(qdisc_lock(qdisc));
> +}
The above looks like a possible shared helper, as mlx code implements a
quite identical function.
Cheers,
Paolo
next prev parent reply other threads:[~2023-02-07 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 5:46 [net-next PATCH V3 0/4] octeontx2-pf: HTB offload support Hariprasad Kelam
2023-02-06 5:46 ` [net-next PATCH V3 1/4] sch_htb: Allow HTB priority parameter in offload mode Hariprasad Kelam
2023-02-06 5:46 ` [net-next PATCH V3 2/4] octeontx2-pf: qos send queues management Hariprasad Kelam
2023-02-07 12:27 ` Paolo Abeni
2023-02-08 17:04 ` [EXT] " Hariprasad Kelam
2023-02-06 5:46 ` [net-next PATCH V3 3/4] octeontx2-pf: Refactor schedular queue alloc/free calls Hariprasad Kelam
2023-02-06 5:46 ` [net-next PATCH V3 4/4] octeontx2-pf: Add support for HTB offload Hariprasad Kelam
2023-02-07 12:48 ` Paolo Abeni [this message]
2023-02-09 16:03 ` Hariprasad Kelam
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=b25f37e4e11d9da5b6d61cbfaa0cafe9889c3926.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hariprasad.netdev@gmail.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxtram95@gmail.com \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=tariqt@nvidia.com \
--cc=xiyou.wangcong@gmail.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).