From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: sparclinux@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH RFC] sparc64: eBPF JIT
Date: Fri, 21 Apr 2017 12:46:40 -0400 (EDT) [thread overview]
Message-ID: <20170421.124640.1134810340055330244.davem@davemloft.net> (raw)
In-Reply-To: <58F50D13.3090001@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Mon, 17 Apr 2017 20:44:35 +0200
> There is samples/bpf/sockex3_kern.c, which exercises it. To
> run it, it would be (clang/llvm needed due to BPF backend not
> available in gcc):
>
> # cd samples/bpf
> # make
> # ./sockex3
> IP src.port -> dst.port bytes packets
> 127.0.0.1.12865 -> 127.0.0.1.49711 148 2
> 127.0.0.1.49711 -> 127.0.0.1.12865 108 2
> [...]
>
> Inside parse_eth_proto(), it will do tail calls based on the
> eth protocol. Over time, we'll move such C based tests over to
> tools/testing/selftests/bpf/.
Ok, after a lot of work setting up an LLVM/CLANG environment and other
things, I implemented tail call support and got this working.
Thanks for the pointers.
next prev parent reply other threads:[~2017-04-21 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 3:38 [PATCH RFC] sparc64: eBPF JIT David Miller
2017-04-17 18:44 ` Daniel Borkmann
2017-04-17 19:03 ` David Miller
2017-04-17 20:55 ` Daniel Borkmann
2017-04-17 20:12 ` David Miller
2017-04-21 16:46 ` David Miller [this message]
2017-04-21 16:50 ` Daniel Borkmann
2017-04-21 18:49 ` Alexei Starovoitov
2017-04-21 19:02 ` David Miller
2017-04-21 19:26 ` Alexei Starovoitov
2017-04-21 19:41 ` David Miller
2017-04-17 23:27 ` Alexei Starovoitov
2017-04-18 1:12 ` David Miller
2017-04-18 5:44 ` Alexei Starovoitov
2017-04-18 18:37 ` David Miller
2017-04-18 22:57 ` Alexei Starovoitov
2017-04-19 2:27 ` David Miller
2017-04-22 1:19 ` David Miller
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=20170421.124640.1134810340055330244.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=sparclinux@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 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).