Lines Matching full:it
30 * In it's _init(9E) routine, it must register itself with the overlay
31 * subsystem. To do this, it allocates an overlay_plugin_register_t via
32 * overlay_plugin_alloc(), that it then * fills out with various required
34 * overlay_plugin_register(). If that succeeds, it should then call
35 * mod_install(9F). If the mod_install(9F) fails, then it should call
36 * overlay_plugin_unregister(). Regardless of success or failure, it should call
41 * called first. It may return an error, such as EBUSY. In such cases, it should
42 * be returned as the return status of _fini(9E). This is quite necessary, it
43 * ensures that if the module is in use it doesn't get unloaded out from under
44 * us the broader subsystem while it's still in use. A driver can use that to
67 * This is the opposite of overlay_plugin_init_t. It will be called when it
77 * type of property it is, the protection of the property (can a user
78 * update it?), whether the property is required, an optional default value
90 * current instance of the plugin. Note, that it is the plugin's
96 * Every overlay device has a corresponding socket that it uses to send and
99 * with other uses of it.
103 * Allow a plugin to set any necessary socket options that it needs on the
105 * for a given mux, if additional devices are added to a mux, it will not
118 * requirement is to decapsulate it and determine what is the correct
125 * This should be set to zero, it's reserved for future use.
170 * sending traffic. For example, vxlan uses UDP, therefore it requires both
200 * that it will probably perform downcalls into different instances in parallel
202 * across instances. If a module finds itself needing that, it will be up to it
203 * to provide it.
206 * the instance has private data, it should likely synchronize it. The one
213 * it cannot make any assumptions about what locks may or may not be held by the
214 * broader system. The only thing that it is safe for it to use are its own
226 * kernel or interrupt context; however, it is guaranteed that the interrupt
227 * will be below LOCK_LEVEL, and therefore it is safe to grab locks.
247 * though today it's either a 24-64 bit value. How should we future