Filter
Top Products
Figure 1-1 HP-DLPI LAN Driver Architecture
PCI Bus
HP-DLPI to
Driver Interface
DLP
I 2.0 API
wit
h
HP Extensions
vi
a STREAMS
Interfaces
Ethernet
Card
HP-DLPI Infrastructure
Tightly Coupled
WSIO Network Interface
Driver for Ethernet
MAC types
HP-UX
Kernel
Services
WSI
O
Services
STREAMS
Services
NetTL
Services
Upper layers of the HP-UX Network Interface Architecture
Data
Link
Layer
Implementation of DLPI 2.0 API and HP extensions to the
API
for use by upper layers
Defines the HP-DLPI to driver interface
Interface repository services for registration and update
of ne
twork interface information
Facilitates option negotiation by the network protocol
layer based on the driver features or options.
Fast path support
Provides connection oriented, connection less and raw
mode se
rvices for use by upper layers
Event notification between upper layers and drivers
Processing of protocol, mulitcast and promiscuous
requests and a repostitory for such control information
Inbound frame processing, including protocol
demultipl
exing, promiscuous/multicast filtering and
handling of IEEE XID/TEST f
rames.
Outbound frame processing: building the LLC/MAC
headers be
fore handoff to drivers
.
.
.
.
.
.
.
.
.
.
For information on writing an HP-DLPI LAN driver, see the HP-UX 11i v3 Driver Development
Guide.
Native STREAMS DLPI LAN Driver Architecture
Native STREAMS DLPI LAN drivers are also known as loosely-coupled drivers. Developers can
continue to have the option of providing a native DLPI implementation for HP-UX 11i v3. This
requires the developer to provide a full DLPI 2.0+HP extensions (for example, DL_HP_PPA_REQ)
support module.
A native LAN driver must do the following:
• Register with HP-DLPI during initialization. This is required because on HP-UX the HP-DLPI
module also acts as the central repository of all networking interfaces installed on the system.
The native STREAMS DLPI driver has its own DLPI implements.
• Inform HP-DLPI every time its hardware state changes.
14 Overview