From: Alexander Alemayhu <alexander@alemayhu.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Alexei Starovoitov <ast@fb.com>,
kernel-team@fb.com
Subject: Re: [RFC net-next 2/2] bpf: Test for bpf_prog ID and BPF_PROG_GET_NEXT_ID
Date: Thu, 27 Apr 2017 09:23:18 +0200 [thread overview]
Message-ID: <20170427072318.GA4734@gmail.com> (raw)
In-Reply-To: <20170427062449.80290-3-kafai@fb.com>
On Wed, Apr 26, 2017 at 11:24:49PM -0700, Martin KaFai Lau wrote:
> Add test to exercise the bpf_prog id generation
> and iteration.
>
Could test_prog_id be a function in tools/testing/selftests/bpf/test_progs.c
instead? bpf_prog_load is already available there.
--
Mit freundlichen Grüßen
Alexander Alemayhu
next prev parent reply other threads:[~2017-04-27 7:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 6:24 [RFC net-next 0/2] Introduce bpf_prog ID and iteration Martin KaFai Lau
2017-04-27 6:24 ` [RFC net-next 1/2] bpf: Introduce bpf_prog ID Martin KaFai Lau
2017-05-15 8:14 ` [lkp-robot] [bpf] de05014aba: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2017-05-15 8:14 ` kernel test robot
2017-05-15 18:57 ` David Miller
2017-05-15 18:57 ` David Miller
2017-04-27 6:24 ` [RFC net-next 2/2] bpf: Test for bpf_prog ID and BPF_PROG_GET_NEXT_ID Martin KaFai Lau
2017-04-27 7:23 ` Alexander Alemayhu [this message]
2017-04-27 21:10 ` Martin KaFai Lau
2017-04-27 13:36 ` [RFC net-next 0/2] Introduce bpf_prog ID and iteration Hannes Frederic Sowa
2017-04-27 21:14 ` Martin KaFai Lau
2017-04-28 1:11 ` prog ID and next steps. Was: " Alexei Starovoitov
2017-04-28 11:50 ` Hannes Frederic Sowa
2017-04-28 18:24 ` Daniel Borkmann
2017-04-28 18:51 ` Hannes Frederic Sowa
2017-04-28 18:57 ` Hannes Frederic Sowa
2017-04-28 19:31 ` Alexei Starovoitov
2017-04-28 21:13 ` Hannes Frederic Sowa
2017-04-30 2:06 ` Alexei Starovoitov
2017-04-30 2:36 ` Hannes Frederic Sowa
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=20170427072318.GA4734@gmail.com \
--to=alexander@alemayhu.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=hannes@stressinduktion.org \
--cc=kafai@fb.com \
--cc=kernel-team@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.