netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: davem@davemloft.net, xiyou.wangcong@gmail.com, jhs@mojatatu.com,
	gerlitz.or@gmail.com, netdev@vger.kernel.org,
	oss-drivers@netronome.com,
	John Hurley <john.hurley@netronome.com>
Subject: Re: [PATCH net-next 7/7] net: sched: call reoffload op on block callback reg
Date: Mon, 25 Jun 2018 23:22:22 +0200	[thread overview]
Message-ID: <20180625212222.GJ2161@nanopsycho> (raw)
In-Reply-To: <20180625141014.61501799@cakuba.netronome.com>

Mon, Jun 25, 2018 at 11:10:14PM CEST, jakub.kicinski@netronome.com wrote:
>On Mon, 25 Jun 2018 22:58:32 +0200, Jiri Pirko wrote:
>> Mon, Jun 25, 2018 at 06:34:31AM CEST, jakub.kicinski@netronome.com wrote:
>> >From: John Hurley <john.hurley@netronome.com>  
>> 
>> [...]	
>> 	
>> >+static int
>> >+tcf_block_playback_offloads(struct tcf_block *block, tc_setup_cb_t *cb,
>> >+			    void *cb_priv, bool add, bool offload_in_use,
>> >+			    struct netlink_ext_ack *extack)
>> >+{
>> >+	struct tcf_chain *chain;
>> >+	struct tcf_proto *tp;
>> >+	int err;
>> >+
>> >+	list_for_each_entry(chain, &block->chain_list, list) {
>> >+		for (tp = rtnl_dereference(chain->filter_chain); tp;
>> >+		     tp = rtnl_dereference(tp->next)) {
>> >+			if (tp->ops->reoffload) {
>> >+				err = tp->ops->reoffload(tp, add, cb, cb_priv,
>> >+							 extack);
>> >+				if (err && add)
>> >+					goto err_playback_remove;
>> >+			} else if (add && offload_in_use) {
>> >+				err = -EOPNOTSUPP;
>> >+				NL_SET_ERR_MSG(extack, "Filter replay failed - a filters doesn't support re-offloading");  
>> 
>> This msg sounds weird. Please fix it.
>
>Indeed..  How about: 
>
>"Filter HW offload failed - classifier without re-offloading support"

Sounds good.

>
>> Otherwise this looks very good to me! Thanks!
>
>Cool, thanks for the comments!  I will respin shortly.

      reply	other threads:[~2018-06-25 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25  4:34 [PATCH net-next 0/7] net: sched: support replay of filter offload when binding to block Jakub Kicinski
2018-06-25  4:34 ` [PATCH net-next 1/7] net: sched: pass extack pointer to block binds and cb registration Jakub Kicinski
2018-06-25  4:34 ` [PATCH net-next 2/7] net: sched: add tcf_proto_op to offload a rule Jakub Kicinski
2018-06-25 20:43   ` Jiri Pirko
2018-06-25  4:34 ` [PATCH net-next 3/7] net: sched: cls_flower: implement offload tcf_proto_op Jakub Kicinski
2018-06-25 20:48   ` Jiri Pirko
2018-06-25  4:34 ` [PATCH net-next 4/7] net: sched: cls_matchall: " Jakub Kicinski
2018-06-25  4:34 ` [PATCH net-next 5/7] net: sched: cls_u32: " Jakub Kicinski
2018-06-25  4:34 ` [PATCH net-next 6/7] net: sched: cls_bpf: " Jakub Kicinski
2018-06-25  4:34 ` [PATCH net-next 7/7] net: sched: call reoffload op on block callback reg Jakub Kicinski
2018-06-25 20:58   ` Jiri Pirko
2018-06-25 21:10     ` Jakub Kicinski
2018-06-25 21:22       ` Jiri Pirko [this message]

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=20180625212222.GJ2161@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=gerlitz.or@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jhs@mojatatu.com \
    --cc=john.hurley@netronome.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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).