From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: davem@davemloft.net, dsahern@gmail.com, aring@mojatatu.com,
daniel@iogearbox.net, alexei.starovoitov@gmail.com,
netdev@vger.kernel.org, oss-drivers@netronome.com,
Quentin Monnet <quentin.monnet@netronome.com>
Subject: Re: [PATCH net-next v4 5/8] net: sched: add extack support for offload via tc_cls_common_offload
Date: Sat, 20 Jan 2018 09:54:48 +0100 [thread overview]
Message-ID: <20180120085448.GA2147@nanopsycho.orion> (raw)
In-Reply-To: <20180120014450.29666-6-jakub.kicinski@netronome.com>
Sat, Jan 20, 2018 at 02:44:47AM CET, jakub.kicinski@netronome.com wrote:
>From: Quentin Monnet <quentin.monnet@netronome.com>
>
>Add extack support for hardware offload of classifiers. In order
>to achieve this, a pointer to a struct netlink_ext_ack is added to the
>struct tc_cls_common_offload that is passed to the callback for setting
>up the classifier. Function tc_cls_common_offload_init() is updated to
>support initialization of this new attribute.
>
>Signed-off-by: Quentin Monnet <quentin.monnet@netronome.com>
>Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>
>---
> include/net/pkt_cls.h | 5 ++++-
> net/sched/cls_bpf.c | 4 ++--
> net/sched/cls_flower.c | 6 +++---
> net/sched/cls_matchall.c | 4 ++--
> net/sched/cls_u32.c | 8 ++++----
> 5 files changed, 15 insertions(+), 12 deletions(-)
>
>diff --git a/include/net/pkt_cls.h b/include/net/pkt_cls.h
>index 2e4b8e436d25..f497f622580b 100644
>--- a/include/net/pkt_cls.h
>+++ b/include/net/pkt_cls.h
>@@ -602,15 +602,18 @@ struct tc_cls_common_offload {
> u32 chain_index;
> __be16 protocol;
> u32 prio;
>+ struct netlink_ext_ack *extack;
> };
>
> static inline void
> tc_cls_common_offload_init(struct tc_cls_common_offload *cls_common,
>- const struct tcf_proto *tp)
>+ const struct tcf_proto *tp,
>+ struct netlink_ext_ack *extack)
> {
> cls_common->chain_index = tp->chain->index;
> cls_common->protocol = tp->protocol;
> cls_common->prio = tp->prio;
>+ cls_common->extack = extack;
> }
[...]
>diff --git a/net/sched/cls_flower.c b/net/sched/cls_flower.c
>index f675a92e1b66..727c10378f37 100644
>--- a/net/sched/cls_flower.c
>+++ b/net/sched/cls_flower.c
>@@ -223,7 +223,7 @@ static void fl_hw_destroy_filter(struct tcf_proto *tp, struct cls_fl_filter *f)
> struct tc_cls_flower_offload cls_flower = {};
> struct tcf_block *block = tp->chain->block;
>
>- tc_cls_common_offload_init(&cls_flower.common, tp);
>+ tc_cls_common_offload_init(&cls_flower.common, tp, NULL);
While you are at it, you should propagate extack whenever possible. For
this, you can easily pass extack to fl_hw_destroy_filter.
Same for other classifiers.
> cls_flower.command = TC_CLSFLOWER_DESTROY;
> cls_flower.cookie = (unsigned long) f;
>
>@@ -243,7 +243,7 @@ static int fl_hw_replace_filter(struct tcf_proto *tp,
> bool skip_sw = tc_skip_sw(f->flags);
> int err;
>
>- tc_cls_common_offload_init(&cls_flower.common, tp);
>+ tc_cls_common_offload_init(&cls_flower.common, tp, extack);
> cls_flower.command = TC_CLSFLOWER_REPLACE;
> cls_flower.cookie = (unsigned long) f;
> cls_flower.dissector = dissector;
>@@ -272,7 +272,7 @@ static void fl_hw_update_stats(struct tcf_proto *tp, struct cls_fl_filter *f)
> struct tc_cls_flower_offload cls_flower = {};
> struct tcf_block *block = tp->chain->block;
>
>- tc_cls_common_offload_init(&cls_flower.common, tp);
>+ tc_cls_common_offload_init(&cls_flower.common, tp, NULL);
For this, it would be probably a bit trickier to get extack, but also
possible.
My motivation is to make the extack always available for users of
tc_cls_common_offload
> cls_flower.command = TC_CLSFLOWER_STATS;
> cls_flower.cookie = (unsigned long) f;
> cls_flower.exts = &f->exts;
[...]
next prev parent reply other threads:[~2018-01-20 8:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 1:44 [PATCH net-next v4 0/8] net: sched: add extack support for cls offloads Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 1/8] net: sched: cls_flower: propagate extack support for filter offload Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 2/8] net: sched: cls_matchall: " Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 3/8] net: sched: cls_u32: " Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 4/8] net: sched: cls_bpf: plumb extack support in filter for hardware offload Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 5/8] net: sched: add extack support for offload via tc_cls_common_offload Jakub Kicinski
2018-01-20 8:54 ` Jiri Pirko [this message]
2018-01-20 10:28 ` Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 6/8] net: sched: create tc_can_offload_extack() wrapper Jakub Kicinski
2018-01-20 8:59 ` Jiri Pirko
2018-01-20 10:12 ` Jakub Kicinski
2018-01-20 10:22 ` Jiri Pirko
2018-01-20 10:33 ` Jakub Kicinski
2018-01-20 10:54 ` Jiri Pirko
2018-01-20 11:12 ` Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 7/8] nfp: bpf: plumb extack into functions related to XDP offload Jakub Kicinski
2018-01-20 1:44 ` [PATCH net-next v4 8/8] nfp: bpf: use extack support to improve debugging Jakub Kicinski
2018-01-22 21:32 ` [PATCH net-next v4 0/8] net: sched: add extack support for cls offloads David Miller
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=20180120085448.GA2147@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=alexei.starovoitov@gmail.com \
--cc=aring@mojatatu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=quentin.monnet@netronome.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).