Lines Matching full:provider

8 dlpi \- Data Link Provider Interface
20 Version 2 of the Data Link Provider Interface (\fBDLPI\fR). \fBDLPI V2\fR
23 provider's protocol. Specifically, the interface is intended to support
28 The interface specifies access to the data link service provider in the form of
32 provider to attach a physical device with physical-level address to a stream,
34 information from the data link provider, exchange data with a peer data link
54 interest occur at the \fBDLPI\fR provider. The negotiation can be performed on
56 DL_NOTIFY_REQ to the provider, which is an M_PROTO message with the following
87 requested types to check if the \fBDLPI\fR provider supports the extension.
89 Upon receiving the DL_NOTIFY_REQ, the \fBDLPI\fR provider must generate a
102 \fBdl_notifications\fR field must include any notifications that the provider
103 supports, along with any other unrequested notifications that the provider
104 supports. However, regardless of the notifications the provider supports, it is
119 message indicates that the DLPI provider does not support the DLPI notification
157 occurred, the \fBDLPI\fR provider must initially generate one or more
160 DL_NOTE_LINK_UP | DL_NOTE_LINK_DOWN, the provider must send a DL_NOTIFY_IND
164 For the initial DL_NOTIFY_IND message, the DLPI provider is strongly
173 The DLPI provider must continue to generate DL_NOTIFY_IND messages until it
175 closed). Further, a DLPI style  2 provider must keep track of the requested
251 provider as \fBM_DATA\fR messages for transmission. \fBDLIOCRAW\fR takes no
284 While a DLPI provider provides its maximum SDU via dl_max_sdu in DL_INFO_ACK
286 provider's media (1500 for Ethernet for example), and not necessarily the
287 absolute maximum amount of data that the provider is able to transmit in a
289 the provider can transmit beyond its advertised maximum SDU. For example, if a
290 DL_ETHER provider can handle packets whose payload section is no greater than
292 the margin would be 22. If a provider supports a non-zero margin, it implements
309 access, data must be sent to a DLPI  provider without link-layer headers (which
310 are added by the provider) and received data is passed to interested DLPI
322 their VLAN headers and must be sent to the DLPI provider with their  VLAN
357 to the DLPI provider for transmission.  Note that the priority value specified
407 A Solaris DLPI link name consists of a \fBDLPI provider name\fR followed by a
411 The DLPI provider name must be between 1 and 16 characters in length, though
412 names between 3 and 8 characters are preferred. The DLPI provider name can
414 The first and last character of the DLPI provider name cannot be a digit.