Lines Matching +full:in +full:- +full:functions

1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
7 functions and types. Every group has its own naming convention
11 All types and functions provided by libbpf API should have one of the
16 --------------------
20 and map one-on-one to corresponding commands.
26 -------
28 Another class of types and functions provided by libbpf API is "objects"
29 and functions to work with them. Objects are high-level abstractions
42 program in ELF object and ``struct bpf_map`` is a map.
44 Functions that work with an object have names built from object name,
56 All objects and corresponding functions other than BTF related should go
57 to ``libbpf.h``. BTF types and functions should go to ``btf.h``.
59 Auxiliary functions
60 -------------------
62 Auxiliary functions and types that don't fit well in any of categories
66 AF_XDP functions
67 -------------------
69 AF_XDP functions should have an ``xsk_`` prefix, e.g.
71 of both low-level ring access functions and high-level configuration
72 functions. These can be mixed and matched. Note that these functions
75 Please take a look at Documentation/networking/af_xdp.rst in the Linux
77 mistakes in case you do not get any traffic up to user space.
84 non-static libbpf symbols should have one of the prefixes mentioned in
89 -----------------
95 .. code-block:: c
100 to be a part of ABI what, in turn, improves both libbpf developer- and
101 user-experiences.
104 ---------------
110 Version name is ``LIBBPF_`` prefix + three-component numeric version,
115 This bump in ABI version is at most once per kernel development cycle.
119 .. code-block::
131 .. code-block::
148 incompatible ones, described in details in [1].
150 Stand-alone build
153 Under https://github.com/libbpf/libbpf there is a (semi-)automated
154 mirror of the mainline's version of libbpf for a stand-alone build.
162 libbpf is dual-licensed under LGPL 2.1 and BSD 2-Clause.