From: David Ahern <dsahern@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>,
alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
oss-drivers@netronome.com
Subject: Re: [PATCH iproute2-next] bpf: don't offload perf array maps
Date: Sat, 5 May 2018 12:23:06 -0600 [thread overview]
Message-ID: <052c3aba-2b21-0793-0f1f-abb430d2e471@gmail.com> (raw)
In-Reply-To: <20180505003751.2232-1-jakub.kicinski@netronome.com>
On 5/4/18 6:37 PM, Jakub Kicinski wrote:
> Perf arrays are handled specially by the kernel, don't request
> offload even when used by an offloaded program.
>
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reviewed-by: Quentin Monnet <quentin.monnet@netronome.com>
> ---
> lib/bpf.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
applied to iproute2-next.
prev parent reply other threads:[~2018-05-05 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 0:37 [PATCH iproute2-next] bpf: don't offload perf array maps Jakub Kicinski
2018-05-05 0:48 ` Daniel Borkmann
2018-05-05 18:23 ` David Ahern [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=052c3aba-2b21-0793-0f1f-abb430d2e471@gmail.com \
--to=dsahern@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=stephen@networkplumber.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