1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
//! # Framework for writing high-performance VPP plugins in Rust
//!
//! [VPP](https://wiki.fd.io/view/VPP/What_is_VPP%3F) is a high performance packet processing
//! with support for a large number of features, and enables writing plugins to extend its
//! functionality.
//!
//! This crate provides the core functionality for writing VPP plugins in Rust. It includes
//! bindings to the VPP C API, as well as abstractions for writing VPP nodes, with the goal of
//! having performance parity with C plugins for fast path packet processing.
//!
//! # Features
//!
//! The following features are available:
//! - `process-node`: Enables infrastructure for using process nodes (using async/await) in VPP
//! plugins.
//! - `experimental`: Used for functionality and types that aren't tested or are not part of the
//! stable API yet as aspects of them might still be under consideration. APIs conditional on
//! this feature may be added, changed or removed without the semantic versioning reflecting
//! this.
// Re-export macros for convenience
pub use vlib_process_node;
pub use ;
/// Re-exported for use by code generated by vpp-plugin-api-gen
pub extern crate bitflags;
/// `VPP_BUILD_VER` of the VPP whose headers this crate was built against.
///
/// Intended for `vlib_plugin_register!`'s `version_required`. VPP's loader compares by prefix: it
/// refuses the plugin unless its own build version *starts with* this string, so a build whose
/// version merely extends it (e.g. `26.06-release-octeon9` for a plugin built against
/// `26.06-release`) still loads it. A plugin that needs the exact build can also compare this
/// with the running VPP's `vlib_plugin_app_version` at init. Empty when the crate was built from
/// the pre-generated bindings (no VPP headers available), which VPP treats as no requirement.
pub const VPP_BUILD_VER: &str = env!;