netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: netdev@vger.kernel.org
Cc: jiri@resnulli.us, gerlitz.or@gmail.com,
	oss-drivers@netronome.com, john.hurley@netronome.com,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [RFC 0/2] net: sched: indirect/remote setup tc block cb registering
Date: Wed,  3 Oct 2018 21:55:09 -0700	[thread overview]
Message-ID: <20181004045511.27733-1-jakub.kicinski@netronome.com> (raw)

Hi!

This set contains a rough RFC implementation of a proposed [1] replacement
for egdev cls_flower offloads.  I did some last minute restructuring
and removal of parts I felt were unnecessary, so if there are glaring bugs
they are probably mine, not John's :)  but hopefully this will give an idea
of the general direction.  We need to beef up the driver part to see how
it fully comes together.

[1] http://vger.kernel.org/netconf2018_files/JakubKicinski_netconf2018.pdf
    slides 10-13

John's says:

This patchset introduces as an alternative to egdev offload by allowing a
driver to register for block updates when an external device (e.g. tunnel
netdev) is bound to a TC block. Drivers can track new netdevs or register
to existing ones to receive information on such events. Based on this,
they may register for block offload rules using already existing
functions.

Included with this RFC is a patch to the NFP driver. This is only supposed
to provide an example of how the remote block setup can be used.

John Hurley (2):
  net: sched: register callbacks for remote tc block binds
  nfp: register remote block callbacks for vxlan/geneve

 .../net/ethernet/netronome/nfp/flower/main.c  |  12 +
 .../net/ethernet/netronome/nfp/flower/main.h  |  10 +
 .../ethernet/netronome/nfp/flower/offload.c   | 156 +++++++++
 .../netronome/nfp/flower/tunnel_conf.c        |   8 +
 include/net/pkt_cls.h                         |  56 ++++
 include/net/sch_generic.h                     |   3 +
 net/sched/cls_api.c                           | 297 +++++++++++++++++-
 7 files changed, 541 insertions(+), 1 deletion(-)

-- 
2.17.1

             reply	other threads:[~2018-10-04 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04  4:55 Jakub Kicinski [this message]
2018-10-04  4:55 ` [RFC 1/2] net: sched: register callbacks for remote tc block binds Jakub Kicinski
2018-10-04  4:55 ` [RFC 2/2] nfp: register remote block callbacks for vxlan/geneve Jakub Kicinski
2018-10-04 14:28 ` [RFC 0/2] net: sched: indirect/remote setup tc block cb registering Or Gerlitz
2018-10-04 15:44   ` John Hurley
2018-10-04 15:53     ` Or Gerlitz
2018-10-04 16:20       ` John Hurley
2018-10-04 17:19         ` Jakub Kicinski
2018-10-10 13:38           ` Or Gerlitz
2018-10-11 11:03             ` John Hurley

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=20181004045511.27733-1-jakub.kicinski@netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=gerlitz.or@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=john.hurley@netronome.com \
    --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).