From: Petar Penkov <peterpenkov96@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
simon.horman@netronome.com, ecree@solarflare.com,
songliubraving@fb.com, tom@herbertland.com,
Petar Penkov <ppenkov@google.com>,
Willem de Bruijn <willemb@google.com>
Subject: [bpf-next, v4 3/5] bpf: support flow dissector in libbpf and bpftool
Date: Fri, 14 Sep 2018 07:46:20 -0700 [thread overview]
Message-ID: <20180914144622.16436-4-peterpenkov96@gmail.com> (raw)
In-Reply-To: <20180914144622.16436-1-peterpenkov96@gmail.com>
From: Petar Penkov <ppenkov@google.com>
This patch extends libbpf and bpftool to work with programs of type
BPF_PROG_TYPE_FLOW_DISSECTOR.
Signed-off-by: Petar Penkov <ppenkov@google.com>
Signed-off-by: Willem de Bruijn <willemb@google.com>
---
tools/bpf/bpftool/prog.c | 1 +
tools/lib/bpf/libbpf.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/tools/bpf/bpftool/prog.c b/tools/bpf/bpftool/prog.c
index dce960d22106..b1cd3bc8db70 100644
--- a/tools/bpf/bpftool/prog.c
+++ b/tools/bpf/bpftool/prog.c
@@ -74,6 +74,7 @@ static const char * const prog_type_name[] = {
[BPF_PROG_TYPE_RAW_TRACEPOINT] = "raw_tracepoint",
[BPF_PROG_TYPE_CGROUP_SOCK_ADDR] = "cgroup_sock_addr",
[BPF_PROG_TYPE_LIRC_MODE2] = "lirc_mode2",
+ [BPF_PROG_TYPE_FLOW_DISSECTOR] = "flow_dissector",
};
static void print_boot_time(__u64 nsecs, char *buf, unsigned int size)
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index 8476da7f2720..9ca8e0e624d8 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -1502,6 +1502,7 @@ static bool bpf_prog_type__needs_kver(enum bpf_prog_type type)
case BPF_PROG_TYPE_CGROUP_SOCK_ADDR:
case BPF_PROG_TYPE_LIRC_MODE2:
case BPF_PROG_TYPE_SK_REUSEPORT:
+ case BPF_PROG_TYPE_FLOW_DISSECTOR:
return false;
case BPF_PROG_TYPE_UNSPEC:
case BPF_PROG_TYPE_KPROBE:
@@ -2121,6 +2122,7 @@ static const struct {
BPF_PROG_SEC("sk_skb", BPF_PROG_TYPE_SK_SKB),
BPF_PROG_SEC("sk_msg", BPF_PROG_TYPE_SK_MSG),
BPF_PROG_SEC("lirc_mode2", BPF_PROG_TYPE_LIRC_MODE2),
+ BPF_PROG_SEC("flow_dissector", BPF_PROG_TYPE_FLOW_DISSECTOR),
BPF_SA_PROG_SEC("cgroup/bind4", BPF_CGROUP_INET4_BIND),
BPF_SA_PROG_SEC("cgroup/bind6", BPF_CGROUP_INET6_BIND),
BPF_SA_PROG_SEC("cgroup/connect4", BPF_CGROUP_INET4_CONNECT),
--
2.19.0.397.gdd90340f6a-goog
next prev parent reply other threads:[~2018-09-14 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:46 [bpf-next, v4 0/5] Introduce eBPF flow dissector Petar Penkov
2018-09-14 14:46 ` [bpf-next, v4 1/5] flow_dissector: implements flow dissector BPF hook Petar Penkov
2018-09-18 18:07 ` Eric Dumazet
2018-09-18 20:40 ` Willem de Bruijn
2018-09-14 14:46 ` [bpf-next, v4 2/5] bpf: sync bpf.h uapi with tools/ Petar Penkov
2018-09-14 14:46 ` Petar Penkov [this message]
2018-09-14 14:46 ` [bpf-next, v4 4/5] flow_dissector: implements eBPF parser Petar Penkov
2018-09-14 14:46 ` [bpf-next, v4 5/5] selftests/bpf: test bpf flow dissection Petar Penkov
2018-09-14 19:22 ` [bpf-next, v4 0/5] Introduce eBPF flow dissector Alexei Starovoitov
2018-09-14 21:47 ` Y Song
2018-09-14 21:49 ` Petar Penkov
2018-09-24 21:14 ` Willem de Bruijn
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=20180914144622.16436-4-peterpenkov96@gmail.com \
--to=peterpenkov96@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=ppenkov@google.com \
--cc=simon.horman@netronome.com \
--cc=songliubraving@fb.com \
--cc=tom@herbertland.com \
--cc=willemb@google.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).