From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: dsahern@gmail.com, jiri@resnulli.us, aring@mojatatu.com,
daniel@iogearbox.net, alexei.starovoitov@gmail.com,
netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net-next v4 0/8] net: sched: add extack support for cls offloads
Date: Mon, 22 Jan 2018 16:32:43 -0500 (EST) [thread overview]
Message-ID: <20180122.163243.1330972091863592386.davem@davemloft.net> (raw)
In-Reply-To: <20180120014450.29666-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Fri, 19 Jan 2018 17:44:42 -0800
> Hi!
>
> I've dropped the tests from the series because test_offloads.py changes
> will conflict with bpf-next patches. I will send four more patches with
> tests once bpf-next is merged back, hopefully still making it into 4.16 :)
>
> v4:
> - rebase on top of Alex's changes.
>
> ---
>
> Quentin says:
>
> This series tries to improve user experience when eBPF hardware offload
> hits error paths at load time. In particular, it introduces netlink
> extended ack support in the nfp driver.
>
> To that aim, transmission of the pointer to the extack object is piped
> through the `change()` operation of the existing classifiers (patch 1 to
> 6). Then it is used for TC offload in the nfp driver (patch 8) and in
> netdevsim (patch 9, selftest in patch 10). Patch 7 adds a helper to handle
> extack messages in the core when TC offload is disabled on the net device.
>
> For completeness extack is propagated for classifiers other than cls_bpf,
> but it's up to the drivers to make use of it.
Series applied, thanks Jakub.
prev parent reply other threads:[~2018-01-22 21:32 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
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 ` David Miller [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=20180122.163243.1330972091863592386.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=aring@mojatatu.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@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).