From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Kicinski <jakub.kicinski@netronome.com>,
alexei.starovoitov@gmail.com
Cc: oss-drivers@netronome.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: offload: add priv field for drivers
Date: Tue, 12 Feb 2019 17:10:41 +0100 [thread overview]
Message-ID: <5af4eee7-437d-0cda-087a-00addffa9d05@iogearbox.net> (raw)
In-Reply-To: <20190212082039.31109-1-jakub.kicinski@netronome.com>
On 02/12/2019 09:20 AM, Jakub Kicinski wrote:
> Currently bpf_offload_dev does not have any priv pointer, forcing
> the drivers to work backwards from the netdev in program metadata.
> This is not great given programs are conceptually associated with
> the offload device, and it means one or two unnecessary deferences.
> Add a priv pointer to bpf_offload_dev.
>
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reviewed-by: Quentin Monnet <quentin.monnet@netronome.com>
Applied, thanks!
prev parent reply other threads:[~2019-02-12 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 8:20 [PATCH bpf-next] bpf: offload: add priv field for drivers Jakub Kicinski
2019-02-12 16:10 ` Daniel Borkmann [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=5af4eee7-437d-0cda-087a-00addffa9d05@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=jakub.kicinski@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).