From: Jesper Dangaard Brouer <brouer@redhat.com>
To: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>
Cc: Alexei Starovoitov <ast@fb.com>,
alexander@alemayhu.com, linux-kernel@vger.kernel.org,
quentin.monnet@6wind.com,
Jesper Dangaard Brouer <brouer@redhat.com>,
Daniel Borkmann <borkmann@iogearbox.net>
Subject: [net-next PATCH 4/4] doc/bpf: describe BCC the BPF Compiler Collection
Date: Tue, 07 Feb 2017 15:30:32 +0100 [thread overview]
Message-ID: <148647783224.10567.17783943294570297203.stgit@localhost> (raw)
In-Reply-To: <148647756092.10567.10947541548678801938.stgit@localhost>
It is worth mentioning BCC (BPF Compiler Collection) in-order
to direct developers into that community.
Reviewed-by: Alexander Alemayhu <alexander@alemayhu.com>
Signed-off-by: Jesper Dangaard Brouer <brouer@redhat.com>
---
Documentation/bpf/bcc_tool_chain.rst | 37 ++++++++++++++++++++++++++++++++++
Documentation/bpf/index.rst | 5 ++---
2 files changed, 39 insertions(+), 3 deletions(-)
create mode 100644 Documentation/bpf/bcc_tool_chain.rst
diff --git a/Documentation/bpf/bcc_tool_chain.rst b/Documentation/bpf/bcc_tool_chain.rst
new file mode 100644
index 000000000000..b721875065bc
--- /dev/null
+++ b/Documentation/bpf/bcc_tool_chain.rst
@@ -0,0 +1,37 @@
+=============================
+BCC (BPF Compiler Collection)
+=============================
+
+BCC is a toolkit to make eBPF programs easier to write, with
+front-ends in Python and Lua. BCC requires LLVM and clang (in version
+3.7.1 or newer) to be available on target, because BCC programs do
+runtime compilation of the restricted-C code into eBPF instructions.
+
+BCC includes several useful tools_ and examples_, developed by
+recognized performance analyst `Brendan Gregg`_ and covered with a
+tutorial_ and slides_.
+
+.. _tools:
+ https://github.com/iovisor/bcc/tree/master/tools
+
+.. _examples:
+ https://github.com/iovisor/bcc/tree/master/examples
+
+.. _`Brendan Gregg`: http://www.brendangregg.com/
+
+.. _tutorial:
+ https://github.com/iovisor/bcc/blob/master/docs/tutorial.md
+
+.. _slides:
+ http://www.slideshare.net/brendangregg/linux-bpf-superpowers/43/
+
+The project maintains an overview of `eBPF supported kernels`_ and
+what versions got which specific features. There is also a `BCC
+Reference Guide`_.
+
+.. _eBPF supported kernels:
+ https://github.com/iovisor/bcc/blob/master/docs/kernel-versions.md
+
+.. _BCC Reference Guide:
+ https://github.com/iovisor/bcc/blob/master/docs/reference_guide.md
+
diff --git a/Documentation/bpf/index.rst b/Documentation/bpf/index.rst
index 618a28f7e959..686cc33fffab 100644
--- a/Documentation/bpf/index.rst
+++ b/Documentation/bpf/index.rst
@@ -35,7 +35,7 @@ the `bpf(2)`_ syscall.
This documentation is focused on the kernel tree's `samples/bpf/`_ and
`tools/lib/bpf/`_. It is worth mentioning that other projects exist,
-like BCC_, that has a slightly different user-facing
+like :doc:`bcc_tool_chain`, that has a slightly different user-facing
syntax, but is interfacing with the same kernel facilities as those
covered by this documentation.
@@ -44,6 +44,7 @@ covered by this documentation.
ebpf_maps
ebpf_maps_types
+ bcc_tool_chain
.. links:
@@ -65,5 +66,3 @@ covered by this documentation.
.. _Traffic control: http://man7.org/linux/man-pages/man8/tc-bpf.8.html
-.. _BCC: https://github.com/iovisor/bcc
-
next prev parent reply other threads:[~2017-02-07 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:30 [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 1/4] doc/bpf: start eBPF documentation tree bpf/ Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 2/4] doc/bpf: document interacting with eBPF maps Jesper Dangaard Brouer
2017-02-07 14:30 ` [net-next PATCH 3/4] doc/bpf: describes the different types of eBPF maps available Jesper Dangaard Brouer
2017-02-07 14:30 ` Jesper Dangaard Brouer [this message]
2017-02-07 15:37 ` [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Jonathan Corbet
2017-02-07 16:09 ` Jesper Dangaard Brouer
2017-02-07 16:46 ` Jonathan Corbet
2017-02-07 20:51 ` Jesper Dangaard Brouer
2017-02-07 21:23 ` Jonathan Corbet
2017-02-08 10:36 ` Jesper Dangaard Brouer
2017-02-07 16:43 ` Daniel Borkmann
2017-02-07 21:19 ` Jesper Dangaard Brouer
2017-02-07 22:32 ` Daniel Borkmann
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=148647783224.10567.17783943294570297203.stgit@localhost \
--to=brouer@redhat.com \
--cc=alexander@alemayhu.com \
--cc=ast@fb.com \
--cc=borkmann@iogearbox.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@6wind.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).