Lines Matching full:it
36 * succeeds, then it should proceed to fill out the registration and then call,
37 * libvarpd_plugin_register() with it. Regardless of whether it succeeds or
38 * fails, it should call libvarpd_plugin_free(). In the case of failure, there
43 * of the operations it defined in the operation vector may be called and
44 * therefore it is recommended that any other required initialization should be
47 * At this time, once a plugin is loaded, it will not be unloaded. Therefore,
68 * consider vxlan, it requires an IP and a port; while a hypothetical nvgre,
71 * A plugin is allowed to describe which of these fields that it supports and
72 * given which encapsulation plugin it is paired with, it can support a varying
74 * It has a notion of a destination port and a destination IP. If it is paired
75 * with a plugin that only requires an IP, then it wouldn't need to show a
83 * additional metadata that it passed in to libvarpd_plugin_register(). The
92 * for the plugin to create and provide any private data that it will
96 * required and it is its job to determine whether or not it supports it.
100 * This is the opposite of varpd_plugin_create_f. It is called to allow the
101 * plugin to reclaim any resources with the private argument that it passed
107 * This is a plugin's chance to verify that it has all of its required
109 * to begin the plugin. After this point it will be legal to have the
115 * This routine is called to indicate that an instance is stopping, it is
121 * This routine is defined by plugins of type OVERLAY_TARGET_POINT. It is
127 * failure, it should return the macro VARPD_LOOKUP_DROP.
132 * It is used to lookup the destination for a given request. Each request
133 * comes in with its own MAC address this allows a plugin to direct it to
136 * This is designed as an asynchronous API. Once a lookup is completed it
138 * argument either VARPD_LOOKUP_OK to indicate that it went alright or it
147 * lifting of validating the packet once it finds that it matches certain
166 * plugin should call libvarpd_plugin_arp_reply and if it was successful,
167 * VARPD_LOOKUP_OK should be passed in and if it failed, VARPD_LOOKUP_DROP
176 * rather than broadcast the initial DHCP request, we instead unicast it to
185 * entry point, it should use VARPD_LOOKUP_OK to indicate that it was
186 * filled in and VARPD_LOOKUP_DROP to indicate that it was not.
198 * always use names to indicate the property it is getting and setting.
209 * value, if it exist, and if relevant, set the valid range of values.
213 * This is used to get the value of a property, if it is set. The passed in
215 * properties. If it is not of sufficient size, the function should return
216 * an error and not update the buffer. Otherwise, it should update the size
222 * that the property is valid before updating it. In addition, it should
228 * that if varpd crashes, it can be recovered. The plugin should write all
229 * state into the nvlist that it is passed in, it may use any keys and
230 * values that it wants. The only consumer of that nvlist will be the
237 * setting properties. The plugin should restore any private state that it
260 * This is the name of the plugin. This is how users will refer to it in
262 * unique across the different plugins, as it will cause others with the