From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Vlad Buslov <vladbu@mellanox.com>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, davem@davemloft.net,
pablo@netfilter.org, Jiri Pirko <jiri@mellanox.com>
Subject: Re: [PATCH net-next 04/10] net: sched: notify classifier on successful offload add/delete
Date: Thu, 22 Aug 2019 15:58:05 -0700 [thread overview]
Message-ID: <20190822155805.6fe6f00c@cakuba.netronome.com> (raw)
In-Reply-To: <20190822124353.16902-5-vladbu@mellanox.com>
On Thu, 22 Aug 2019 15:43:47 +0300, Vlad Buslov wrote:
> diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
> index 4215c849f4a3..d8ef7a9e6906 100644
> --- a/net/sched/cls_api.c
> +++ b/net/sched/cls_api.c
> @@ -3099,9 +3099,13 @@ int tc_setup_cb_add(struct tcf_block *block, struct tcf_proto *tp,
> }
>
> ok_count = __tc_setup_cb_call(block, type, type_data, err_stop);
> - if (ok_count > 0)
> - tc_cls_offload_cnt_update(block, tp, in_hw_count, flags,
> - ok_count, true);
> + if (ok_count >= 0) {
> + if (tp->ops->hw_add)
> + tp->ops->hw_add(tp, type_data);
> + if (ok_count > 0)
> + tc_cls_offload_cnt_update(block, tp, in_hw_count, flags,
> + ok_count, true);
> + }
nit:
if (ok_count < 0)
goto err_unlock;
if (tp->ops->hw_add)
tp->ops->hw_add(tp, type_data);
if (ok_count > 0)
tc_cls_offload_cnt_update(block, tp, in_hw_count, flags,
ok_count, true);
IOW try to keep the "success flow" unindented.
> errout:
> up_read(&block->cb_lock);
> return ok_count;
next prev parent reply other threads:[~2019-08-22 22:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 12:43 [PATCH net-next 00/10] Refactor cls hardware offload API to support rtnl-independent drivers Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 01/10] net: sched: protect block offload-related fields with rw_semaphore Vlad Buslov
2019-08-22 22:15 ` Jakub Kicinski
2019-08-23 10:25 ` Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 02/10] net: sched: change tcf block offload counter type to atomic_t Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 03/10] net: sched: refactor block offloads counter usage Vlad Buslov
2019-08-22 22:53 ` Jakub Kicinski
2019-08-23 10:39 ` Vlad Buslov
2019-08-23 18:26 ` Jakub Kicinski
2019-08-22 12:43 ` [PATCH net-next 04/10] net: sched: notify classifier on successful offload add/delete Vlad Buslov
2019-08-22 22:58 ` Jakub Kicinski [this message]
2019-08-22 12:43 ` [PATCH net-next 05/10] net: sched: add API for registering unlocked offload block callbacks Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 06/10] net: sched: conditionally obtain rtnl lock in cls hw offloads API Vlad Buslov
2019-08-22 23:03 ` Jakub Kicinski
2019-08-23 10:42 ` Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 07/10] net: sched: take rtnl lock in tc_setup_flow_action() Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 08/10] net: sched: take reference to action dev before calling offloads Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 09/10] net: sched: copy tunnel info when setting flow_action entry->tunnel Vlad Buslov
2019-08-22 12:43 ` [PATCH net-next 10/10] net: sched: flower: don't take rtnl lock for cls hw offloads API Vlad Buslov
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=20190822155805.6fe6f00c@cakuba.netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vladbu@mellanox.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).