From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net
Subject: Re: [PATCHv7 net-next 00/15] BPF hardware offload (cls_bpf for now)
Date: Wed, 21 Sep 2016 19:56:00 -0400 (EDT) [thread overview]
Message-ID: <20160921.195600.1809838520295604067.davem@davemloft.net> (raw)
In-Reply-To: <1474454647-20137-1-git-send-email-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Wed, 21 Sep 2016 11:43:52 +0100
> In the last year a lot of progress have been made on offloading
> simpler TC classifiers. There is also growing interest in using
> BPF for generic high-speed packet processing in the kernel.
> It seems beneficial to tie those two trends together and think
> about hardware offloads of BPF programs. This patch set presents
> such offload to Netronome smart NICs. cls_bpf is extended with
> hardware offload capabilities and NFP driver gets a JIT translator
> which in presence of capable firmware can be used to offload
> the BPF program onto the card.
>
> BPF JIT implementation is not 100% complete (e.g. missing instructions)
> but it is functional. Encouragingly it should be possible to
> offload most (if not all) advanced BPF features onto the NIC -
> including packet modification, maps, tunnel encap/decap etc.
...
Series applied, thanks.
prev parent reply other threads:[~2016-09-21 23:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 10:43 [PATCHv7 net-next 00/15] BPF hardware offload (cls_bpf for now) Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 01/15] net: cls_bpf: add hardware offload Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 02/15] net: cls_bpf: limit hardware offload by software-only flag Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 03/15] net: cls_bpf: add support for marking filters as hardware-only Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 04/15] bpf: don't (ab)use instructions to store state Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 05/15] bpf: expose internal verfier structures Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 06/15] bpf: enable non-core use of the verfier Jakub Kicinski
2016-09-21 10:43 ` [PATCHv7 net-next 07/15] bpf: recognize 64bit immediate loads as consts Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 08/15] nfp: add BPF to NFP code translator Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 09/15] nfp: bpf: add hardware bpf offload Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 10/15] net: cls_bpf: allow offloaded filters to update stats Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 11/15] nfp: bpf: " Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 12/15] nfp: bpf: add packet marking support Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 13/15] net: act_mirred: allow statistic updates from offloaded actions Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 14/15] nfp: bpf: add support for legacy redirect action Jakub Kicinski
2016-09-21 10:44 ` [PATCHv7 net-next 15/15] nfp: bpf: add offload of TC direct action mode Jakub Kicinski
2016-09-21 10:48 ` [PATCHv7 net-next 00/15] BPF hardware offload (cls_bpf for now) Jakub Kicinski
2016-09-21 13:35 ` Daniel Borkmann
2016-09-21 23:56 ` 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=20160921.195600.1809838520295604067.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
/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).