Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
34 lines
1.1 KiB
ReStructuredText
34 lines
1.1 KiB
ReStructuredText
.. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
|
|
|
|
.. _libbpf:
|
|
|
|
======
|
|
libbpf
|
|
======
|
|
|
|
If you are looking to develop BPF applications using the libbpf library, this
|
|
directory contains important documentation that you should read.
|
|
|
|
To get started, it is recommended to begin with the :doc:`libbpf Overview
|
|
<libbpf_overview>` document, which provides a high-level understanding of the
|
|
libbpf APIs and their usage. This will give you a solid foundation to start
|
|
exploring and utilizing the various features of libbpf to develop your BPF
|
|
applications.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
|
|
libbpf_overview
|
|
API Documentation <https://libbpf.readthedocs.io/en/latest/api.html>
|
|
program_types
|
|
libbpf_naming_convention
|
|
libbpf_build
|
|
|
|
|
|
All general BPF questions, including kernel functionality, libbpf APIs and their
|
|
application, should be sent to bpf@vger.kernel.org mailing list. You can
|
|
`subscribe <http://vger.kernel.org/vger-lists.html#bpf>`_ to the mailing list
|
|
search its `archive <https://lore.kernel.org/bpf/>`_. Please search the archive
|
|
before asking new questions. It may be that this was already addressed or
|
|
answered before.
|