Commit 4d496be9 authored by David Vernet's avatar David Vernet Committed by Alexei Starovoitov

bpf,docs: Create new standardization subdirectory

The BPF standardization effort is actively underway with the IETF. As
described in the BPF Working Group (WG) charter in [0], there are a
number of proposed documents, some informational and some proposed
standards, that will be drafted as part of the standardization effort.

[0]: https://datatracker.ietf.org/wg/bpf/about/

Though the specific documents that will formally be standardized will
exist as Internet Drafts (I-D) and WG documents in the BPF WG
datatracker page, the source of truth from where those documents will be
generated will reside in the kernel documentation tree (originating in
the bpf-next tree).

Because these documents will be used to generate the I-D and WG
documents which will be standardized with the IETF, they are a bit
special as far as kernel-tree documentation goes:

- They will be dual licensed with LGPL-2.1 OR BSD-2-Clause
- IETF I-D and WG documents (the documents which will actually be
  standardized) will be auto-generated from these documents.

In order to keep things clearly organized in the BPF documentation tree,
and to make it abundantly clear where standards-related documentation
needs to go, we should move standards-relevant documents into a separate
standardization/ subdirectory.
Signed-off-by: default avatarDavid Vernet <void@manifault.com>
Link: https://lore.kernel.org/r/20230710183027.15132-1-void@manifault.comSigned-off-by: default avatarAlexei Starovoitov <ast@kernel.org>
parent 19f4b532
...@@ -12,9 +12,9 @@ that goes into great technical depth about the BPF Architecture. ...@@ -12,9 +12,9 @@ that goes into great technical depth about the BPF Architecture.
.. toctree:: .. toctree::
:maxdepth: 1 :maxdepth: 1
instruction-set
verifier verifier
libbpf/index libbpf/index
standardization/index
btf btf
faq faq
syscall_api syscall_api
...@@ -29,7 +29,6 @@ that goes into great technical depth about the BPF Architecture. ...@@ -29,7 +29,6 @@ that goes into great technical depth about the BPF Architecture.
bpf_licensing bpf_licensing
test_debug test_debug
clang-notes clang-notes
linux-notes
other other
redirect redirect
......
.. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
===================
BPF Standardization
===================
This directory contains documents that are being iterated on as part of the BPF
standardization effort with the IETF. See the `IETF BPF Working Group`_ page
for the working group charter, documents, and more.
.. toctree::
:maxdepth: 1
instruction-set
linux-notes
.. Links:
.. _IETF BPF Working Group: https://datatracker.ietf.org/wg/bpf/about/
...@@ -45,7 +45,8 @@ On Linux, this integer is a BTF ID. ...@@ -45,7 +45,8 @@ On Linux, this integer is a BTF ID.
Legacy BPF Packet access instructions Legacy BPF Packet access instructions
===================================== =====================================
As mentioned in the `ISA standard documentation <instruction-set.rst#legacy-bpf-packet-access-instructions>`_, As mentioned in the `ISA standard documentation
<instruction-set.html#legacy-bpf-packet-access-instructions>`_,
Linux has special eBPF instructions for access to packet data that have been Linux has special eBPF instructions for access to packet data that have been
carried over from classic BPF to retain the performance of legacy socket carried over from classic BPF to retain the performance of legacy socket
filters running in the eBPF interpreter. filters running in the eBPF interpreter.
......
...@@ -3746,7 +3746,7 @@ R: David Vernet <void@manifault.com> ...@@ -3746,7 +3746,7 @@ R: David Vernet <void@manifault.com>
L: bpf@vger.kernel.org L: bpf@vger.kernel.org
L: bpf@ietf.org L: bpf@ietf.org
S: Maintained S: Maintained
F: Documentation/bpf/instruction-set.rst F: Documentation/bpf/standardization/
BPF [GENERAL] (Safe Dynamic Programs and Tools) BPF [GENERAL] (Safe Dynamic Programs and Tools)
M: Alexei Starovoitov <ast@kernel.org> M: Alexei Starovoitov <ast@kernel.org>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment