From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Kicinski <jakub.kicinski@netronome.com>,
alexei.starovoitov@gmail.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH bpf 0/2] bpf: fix the load time reporting and make offload test more resilient
Date: Fri, 15 Jun 2018 03:15:53 +0200 [thread overview]
Message-ID: <a6d7771f-0817-599b-cf9e-aad6c6a142a8@iogearbox.net> (raw)
In-Reply-To: <20180614180656.14550-1-jakub.kicinski@netronome.com>
On 06/14/2018 08:06 PM, Jakub Kicinski wrote:
> Hi!
>
> This small series allows test_offload.py selftest to run on modern
> distributions which may create BPF programs for cgroups at boot,
> like Ubuntu 18.04. We still expect the program list to not be
> altered by any other agent while the test is running, but no longer
> depend on there being no BPF programs at all at the start.
>
> Fixing the test revealed a small problem with bpftool, which doesn't
> report the program load time very accurately. Because nanoseconds
> were not taken into account reported load time would fluctuate by
> 1 second. First patch of the series takes care of fixing that.
>
> Jakub Kicinski (2):
> tools: bpftool: improve accuracy of load time
> selftests/bpf: test offloads even with BPF programs present
>
> tools/bpf/bpftool/prog.c | 4 +++-
> tools/testing/selftests/bpf/test_offload.py | 12 ++++++++++--
> 2 files changed, 13 insertions(+), 3 deletions(-)
>
Applied to bpf, thanks Jakub!
prev parent reply other threads:[~2018-06-15 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:06 [PATCH bpf 0/2] bpf: fix the load time reporting and make offload test more resilient Jakub Kicinski
2018-06-14 18:06 ` [PATCH bpf 1/2] tools: bpftool: improve accuracy of load time Jakub Kicinski
2018-06-14 18:06 ` [PATCH bpf 2/2] selftests/bpf: test offloads even with BPF programs present Jakub Kicinski
2018-06-15 1:15 ` 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=a6d7771f-0817-599b-cf9e-aad6c6a142a8@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).