hxge(7d) - osol9

1hxge(7D)                            Devices                           hxge(7D)
2
3
4

NAME

6       hxge - Sun Blade 10 Gigabit Ethernet network driver
7

SYNOPSIS

9       /dev/hxge*
10
11

DESCRIPTION

13       The  hxge  Gigabit Ethernet driver is a multi-threaded, loadable, clon‐
14       able, GLD-based STREAMS driver supporting the Data Link Provider Inter‐
15       face, dlpi(7P), on the Sun Blade Shared 10Gb Ethernet Interface.
16
17
18       The  Shared PCI-Express 10 Gb networking interface provides network I/O
19       consolidation for up to six Constellation blades, with each blade  see‐
20       ing its own portion of the network interface.
21
22
23       The  hxge  driver functions include chip initialization, frame transmit
24       and receive, flow classification, multicast and promiscuous support and
25       error recovery and reporting in the blade domain.
26

APPLICATION PROGRAMMING INTERFACE

28       The cloning character-special device, /dev/hxge, is used  to access Sun
29       Blade Shared 10Gb Ethernet Interface devices installed within the  sys‐
30       tem.
31
32
33       The hxge driver is managed by the dladm(1M) command line utility, which
34       allows VLANs to be defined on top  of  hxge   instances  and  for  hxge
35       instances to be aggregated. See dladm(1M) for more details.
36
37
38       You must send an explicit DL_ATTACH_REQ message to associate the opened
39       stream with a particular device (PPA). The PPA ID is interpreted as  an
40       unsigned  integer  data  type  and  indicates  the corresponding device
41       instance (unit) number. The driver returns an error  (DL_ERROR_ACK)  if
42       the PPA field value does not correspond to a valid device instance num‐
43       ber for the system. The device is initialized  on   first   attach  and
44       de-initialized (stopped) at last detach
45
46
47       The  values  returned  by  the  driver  in the DL_INFO_ACK primitive in
48       response to a DL_INFO_REQ are:
49
50           o      Maximum SDU is  1500  (ETHERMTU  -  defined  in  <sys/ether‐
51                  net.h>).
52
53           o      Minimum SDU is 0.
54
55           o      DLSAP address length is 8.
56
57           o      MAC type is DL_ETHER.
58
59           o      SAP  length value is -2, meaning the physical address compo‐
60                  nent is followed  immediately  by  a  2-byte  SAP  component
61                  within the DLSAP address.
62
63           o      Broadcast  address  value  is  the  Ethernet/IEEE  broadcast
64                  address (FF:FF:FF:FF:FF:FF).
65
66                  Due to the nature of the link address definition for  IPoIB,
67                  the DL_SET_PHYS_ADDR_REQ DLPI primitive is not supported.
68
69                  In  the  transmit case for streams that have been put in raw
70                  mode via the  DLIOCRAW  ioctl,  the  dlpi  application  must
71                  prepend the 20 byte IPoIB destination address to the data it
72                  wants to transmit over-the-wire. In the receive case, appli‐
73                  cations  receive  the  IP/ARP  datagram  along with the IETF
74                  defined 4 byte header.
75
76
77       Once in the DL_ATTACHED state, you must send a DL_BIND_REQ to associate
78       a particular Service Access Point (SAP) with the stream.
79

CONFIGURATION

81       The link speed and mode are fixed at 10 Gbps full-duplex.
82
83
84       The  default  MTU is 1500. To enable jumbo frame support, you configure
85       the hxge driver by defining the  accept-jumbo  property  to  1  in  the
86       hxge.conf file. Note that the largest jumbo size is 9178 bytes.
87
88
89       The  driver may be configured to discard certain classes of traffic. By
90       default, no class of traffic is allowed. You configure the hxge  driver
91       by  defining  the class option property to 0x20000 in hxge.conf to dis‐
92       card the specified class of traffic. For example, the following line in
93       hxge.conf discards all IP Version 4 TCP traffic:
94
95         class-opt-ipv4-tcp = 0x20000;
96
97
98
99       You  can  also  use the ndd(1M) command to configure the hxge driver at
100       runtime to discard any classes of traffic.
101
102
103       The hxgedriver supports the self-healing functionality of  Solaris  OS.
104       By   default   it   is   configured  to       DDI_FM_EREPORT_CAPABLE  |
105       DDI_FM_ERRCB_CAPABLE. You configure the hxge driver by defining the fm-
106       capable  property  in hxge.conf to other capabilities or to 0x0 to dis‐
107       able it entirely.
108
109
110       The hxge driver may be configured using the standard ifconfig(1M)  com‐
111       mand.
112
113
114       The  hxge  driver also reports various hardware and software statistics
115       data. You can view these statistics using the kstat(1M) command.
116

FILES

118       /dev/hxge*                  Special character device.
119
120
121       /kernel/drv/hxge            32-bit device driver (x86).
122
123
124       /kernel/drv/sparcv9/hxge    64-bit device driver (SPARC).
125
126
127       /kernel/drv/amd64/hxge      64-bit device driver (x86).
128
129
130       /kernel/drv/hxge.conf       Configuration file.
131
132

ATTRIBUTES

134       See attributes(5) for descriptions of the following attributes:
135
136
137
138
139       ┌─────────────────────────────┬─────────────────────────────┐
140       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
141       ├─────────────────────────────┼─────────────────────────────┤
142       │Architecture                 │SPARC, x86                   │
143       └─────────────────────────────┴─────────────────────────────┘
144