Lines Matching refs:protocol

1 Description of the "concap" encapsulation protocol interface
5 drivers that need to process an encapsulation protocol. 
6 It is assumed that the protocol interacts with a linux network device by
22 The encapsulation protocol used on top of WAN connections or permanent
28 encapsulation protocols. The encapsulation protocol is configured by a
31 depending on the currently configured encapsulation protocol.
34 protocol which is unique to the hardware type of the interface. The LAN
37 encapsulation protocol directly (usually by just providing a hard_header()
43    The configurability of the encapsulation protocol to be used
64 protocol, complexity could be reduced and maintainability could be
68 Likewise, a similar encapsulation protocol will frequently be needed by
72 similar code in them. By cleanly separating the encapsulation protocol
83 the encapsulation protocol used, e.g. for a ppp module using our service
91 The encapsulation protocol currently provides the following
94 - create a new encapsulation protocol instance
95 - delete encapsulation protocol instance and free all its resources
96 - initialize (open) the encapsulation protocol instance for use.
97 - deactivate (close) an encapsulation protocol instance.
98 - process (xmit) data handed down by upper protocol layer
105 provided by the encapsulation protocol instance within a
110 	/* create a new encapsulation protocol instance of same type */
113 	/* delete encapsulation protocol instance and free all its resources.
117 	/* initialize the protocol's data. To be called at interface startup
119 	   encapsulation protocol may be used after this*/
124 	/* deactivate an encapsulation protocol instance. The encapsulation
125 	   protocol may not call any *dops methods after this. */
146 some service primitives to the encapsulation protocol:
152 The encapsulation protocol accesses those primitives via callbacks
170 because the encapsulation protocol directly calls netif_rx(). 
175 An encapsulation protocol itself is actually the
181 	void *proto_data;               /* protocol specific private data, to
190 Most of this is filled in when the device requests the protocol to 
208 	struct concap_proto *cprot;        /* callbacks provided by protocol */
216 The concept of the concap proto might help to reuse protocol code and
219 when processing the protocol. This has of course some impact on
234 e.g. instead of the concap protocol's service function
243 driver could directly register the concap protocol's encap_and_xmit()
252 This might even allow for some protocol stacking. And the network
255 protocol is configured. Thus, eliminating the performance penalty
256 of the concap interface when a trivial concap protocol is used.
258 protocol configuration.