mptcpd
Multipath TCP Daemon
|
mptcpd user space path manager plugin header file. More...
Go to the source code of this file.
Classes | |
struct | mptcpd_plugin_desc |
Plugin-specific characteristics / descriptor. More... | |
struct | mptcpd_plugin_ops |
Mptcpd plugin interface. More... | |
Macros | |
#define | MPTCPD_PLUGIN_SYM _mptcpd_plugin |
Symbol name of mptcpd plugin characterstics. | |
#define | MPTCPD_PLUGIN_DEFINE(name, description, priority, init, exit) |
Define mptcpd plugin characterstics. | |
#define | MPTCPD_PLUGIN_PRIORITY_LOW 19 |
Low plugin priority. | |
#define | MPTCPD_PLUGIN_PRIORITY_DEFAULT 0 |
Default plugin priority. | |
#define | MPTCPD_PLUGIN_PRIORITY_HIGH -20 |
High plugin priority. | |
Functions | |
MPTCPD_API bool | mptcpd_plugin_register_ops (char const *name, struct mptcpd_plugin_ops const *ops) |
Register path manager operations. | |
mptcpd user space path manager plugin header file.
Copyright (c) 2017-2020, 2022, Intel Corporation
#define MPTCPD_PLUGIN_DEFINE | ( | name, | |
description, | |||
priority, | |||
init, | |||
exit | |||
) |
Define mptcpd plugin characterstics.
Mptcpd plugins should use this macro to define and export characterstics (descriptor) required by mptcpd.
[in] | name | Plugin name (unquoted) |
[in] | description | Plugin description |
[in] | priority | Plugin priority, where the higher values are lower in priority, and lower values are higher in priority, similar to how process scheduling priorities are defined. Mptcpd defines convenience plugin priorities MPTCP_PLUGIN_PRIORITY_LOW , MPTCP_PLUGIN_PRIORITY_DEFAULT , and MPTCP_PLUGIN_PRIORITY_HIGH . |
[in] | init | Function called when mptcpd initializes the plugin. |
[in] | exit | Function called when mptcpd finalizes the plugin. |
#define MPTCPD_PLUGIN_SYM _mptcpd_plugin |
Symbol name of mptcpd plugin characterstics.
MPTCPD_API bool mptcpd_plugin_register_ops | ( | char const * | name, |
struct mptcpd_plugin_ops const * | ops | ||
) |
Register path manager operations.
Path manager plugins should call this function in their init
function to register their MPTCP path manager event handling functions.
[in] | name | Plugin name. |
[in] | ops | Set of MPTCP path manager event handling functions provided by the path manager plugin. |
true | Registration succeeded. |
false | Registration failed. Failure should only occur if plugins were not loaded prior to calling this function. Plugin developers should generally not have to worry about that since the load is guaranteed to have occurred prior to their init function being called. |
false
if all of the callbacks in ops are NULL
?