Lines Matching full:functions

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
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
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
62 Auxiliary functions and types that don't fit well in any of categories
66 AF_XDP functions
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