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 0/4] Documenting eBPF - extended Berkeley Packet Filter
Date: Tue, 07 Feb 2017 15:30:11 +0100 [thread overview]
Message-ID: <148647756092.10567.10947541548678801938.stgit@localhost> (raw)
Question: What kernel tree should this go into???
If going through Jonathan Corbet, will it appear sooner here???
https://www.kernel.org/doc/html/latest/
If it will not appear sooner that way, then it's likely best to keep
it in sync with the tree that takes eBPF code changes.
This marks the beginning of user-facing developer documentation for
using eBPF (extended Berkeley Packet Filter) as part of the kernel
Documentation/ tree.
This documentation is also available here[1], as an intermidiate quick
way of prototyping and releasing the documentation. The autoriative
and official version of the documentation is what gets included in the
kernel tree. The docs at [2] will get updated based on what gets
accepted after the standard peer-review kernel process.
[1] http://prototype-kernel.readthedocs.io/en/latest/bpf/index.html
[2] https://github.com/netoptimizer/prototype-kernel/tree/master/kernel/Documentation
Thanks to the following people, who have already reviewed and fixed
earlier versions of this documentation on the IOvisor mailing-list:
Alexander Alemayhu <alexander@alemayhu.com>
Alexei Starovoitov <ast@fb.com>
Daniel Borkmann <daniel@iogearbox.net>
Quentin Monnet <quentin.monnet@6wind.com>
---
Jesper Dangaard Brouer (4):
doc/bpf: start eBPF documentation tree bpf/
doc/bpf: document interacting with eBPF maps
doc/bpf: describes the different types of eBPF maps available
doc/bpf: describe BCC the BPF Compiler Collection
Documentation/bpf/bcc_tool_chain.rst | 37 +++++
Documentation/bpf/ebpf_maps.rst | 256 +++++++++++++++++++++++++++++++++
Documentation/bpf/ebpf_maps_types.rst | 119 +++++++++++++++
Documentation/bpf/index.rst | 68 +++++++++
Documentation/index.rst | 1
5 files changed, 481 insertions(+)
create mode 100644 Documentation/bpf/bcc_tool_chain.rst
create mode 100644 Documentation/bpf/ebpf_maps.rst
create mode 100644 Documentation/bpf/ebpf_maps_types.rst
create mode 100644 Documentation/bpf/index.rst
--
next 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 Jesper Dangaard Brouer [this message]
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 ` [net-next PATCH 4/4] doc/bpf: describe BCC the BPF Compiler Collection Jesper Dangaard Brouer
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=148647756092.10567.10947541548678801938.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