From: daniel@iogearbox.net (Daniel Borkmann)
To: linux-arm-kernel@lists.infradead.org
Subject: arch: arm: bpf: Converting cBPF to eBPF for arm 32 bit
Date: Wed, 29 Mar 2017 02:00:08 +0200 [thread overview]
Message-ID: <58DAF908.8010404@iogearbox.net> (raw)
In-Reply-To: <CAHgaXd+4QkFxnt-_iCqH8AyCN_Y8gXwr+y=iugz38NKSWspsbA@mail.gmail.com>
Hi Shubham,
On 03/28/2017 10:49 PM, Shubham Bansal wrote:
[...]
> Do you have any document to understand the working of tail calls? I
> looked at your presentations but it seemed confusing to me. Anything
> simple would be great, just about the tail calls. I don't think I need
> examples, I can get them from your presentations. I just need a very
> general idea. May be you know the code in kernel where it is
> implemented.
Sure, it's in __bpf_prog_run(), see the JMP_TAIL_CALL (kernel/bpf/core.c +1019).
That's effectively what JITs implement. [1] page 3 has a high-level description
as well, hope that helps.
Thanks,
Daniel
[1] http://www.netdevconf.org/1.1/proceedings/papers/On-getting-tc-classifier-fully-programmable-with-cls-bpf.pdf
next prev parent reply other threads:[~2017-03-29 0:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 10:38 arch: arm: bpf: Converting cBPF to eBPF for arm 32 bit Shubham Bansal
2017-01-30 21:57 ` Kees Cook
[not found] ` <CAHgaXd+nj69n-Xf46N=4M-j-0hKHVrrLfsvRZCG=2CCAtVF6ZA@mail.gmail.com>
[not found] ` <CAGXu5j+NSLomuSgD40kys+pWc+J9aB6Bbk_gSP9Lp_ScimQn_w@mail.gmail.com>
2017-02-01 13:01 ` Shubham Bansal
[not found] ` <76621BFF-B30B-4417-AB2B-DB21CA6092D9@netronome.com>
2017-02-03 7:04 ` Shubham Bansal
2017-02-03 8:25 ` nick viljoen
2017-02-08 7:29 ` Shubham Bansal
2017-02-08 19:41 ` Kees Cook
2017-03-15 12:13 ` Shubham Bansal
2017-03-15 21:55 ` David Miller
2017-03-28 20:49 ` Shubham Bansal
2017-03-29 0:00 ` Daniel Borkmann [this message]
2017-03-30 14:04 ` Shubham Bansal
2017-04-06 11:05 ` Shubham Bansal
2017-04-06 12:51 ` Daniel Borkmann
2017-05-06 16:48 ` Shubham Bansal
2017-05-06 18:38 ` David Miller
2017-05-06 20:27 ` Shubham Bansal
2017-05-06 22:17 ` Shubham Bansal
2017-05-09 20:12 ` Shubham Bansal
2017-05-09 20:19 ` David Miller
2017-05-09 20:25 ` Daniel Borkmann
[not found] <CAHgaXdKsO2xoKYp7g91g+n+d_1KHSSByLjzBB-WjVXSjhB7qxw@mail.gmail.com>
[not found] ` <20170510.212952.1440495072777358778.davem@davemloft.net>
[not found] ` <CAHgaXdK8LEEUPm4jTRRzCnjwdWAauHmmB=caZsSFY8MmStH89Q@mail.gmail.com>
[not found] ` <20170510.215218.2185526627014393313.davem@davemloft.net>
[not found] ` <CAHgaXdKZ_v+iO7uqEDx7PA7D+xcp1FngGvJ1SRSsGXNQ-iWWDQ@mail.gmail.com>
2017-05-11 9:32 ` Shubham Bansal
2017-05-11 15:30 ` Kees Cook
2017-05-13 21:38 ` Shubham Bansal
2017-05-15 17:44 ` Kees Cook
2017-05-15 19:55 ` Daniel Borkmann
2017-05-20 20:01 ` Shubham Bansal
2017-05-22 13:01 ` Daniel Borkmann
2017-05-22 17:04 ` Shubham Bansal
2017-05-22 20:05 ` Kees Cook
2017-05-23 2:58 ` Shubham Bansal
2017-05-23 4:27 ` Kees Cook
2017-05-22 18:58 ` Kees Cook
2017-05-22 19:08 ` Florian Fainelli
2017-05-23 3:34 ` Shubham Bansal
2017-05-23 4:22 ` Kees Cook
2017-05-23 5:03 ` Shubham Bansal
2017-05-23 5:35 ` Kees Cook
[not found] ` <CAHgaXdJa9uJYO3bODuzDRaqOas0i=zMk0jioWFXKm_=UJRtVrw@mail.gmail.com>
2017-05-23 19:32 ` Kees Cook
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=58DAF908.8010404@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=linux-arm-kernel@lists.infradead.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).