View | Details | Raw Unified | Return to bug 158813
Collapse All | Expand All

(-)jme.4 (-25 / +30 lines)
Lines 24-30 Link Here
24 
.\"
 24 
.\"
25 
.\" $FreeBSD: src/share/man/man4/jme.4,v 1.5 2011/06/29 17:32:52 yongari Exp $
 25 
.\" $FreeBSD: src/share/man/man4/jme.4,v 1.5 2011/06/29 17:32:52 yongari Exp $
26 
.\"
 26 
.\"
27 
.Dd June 29, 2011
 27 
.Dd July 11, 2011
28 
.Dt JME 4
 28 
.Dt JME 4
29 
.Os
 29 
.Os
30 
.Sh NAME
 30 
.Sh NAME
Lines 130-152 Link Here
130 
tunables:
 130 
tunables:
131 
.Bl -tag -width "xxxxxx"
 131 
.Bl -tag -width "xxxxxx"
132 
.It Va dev.jme.%d.tx_coal_to
 132 
.It Va dev.jme.%d.tx_coal_to
133 
Maximum amount of time to delay for Tx completion interrupt in
 133 
This variable sets the
134 
units of 1us.
 134 
maximum amount of time to delay before sending a Tx completion interrupt, in
135 
The accepted range is 1 to 65535, the default is 100 (100us).
 135 
microseconds.
136 
The accepted range is 1 to 65535; the default is 100 (100us).
136 
.It Va dev.jme.%d.tx_coal_pkt
 137 
.It Va dev.jme.%d.tx_coal_pkt
137 
Maximum number of packets to fire Tx completion interrupt.
 138 
This variable sets the maximum number of outgoing packets which may be
138 
The accepted range is 1 to 255, the default is 8.
 139 
coalesced together into a single Tx completion interrupt.
140 
The accepted range is 1 to 255; the default is 8.
139 
.It Va dev.jme.%d.rx_coal_to
 141 
.It Va dev.jme.%d.rx_coal_to
140 
Maximum amount of time to delay for Rx completion interrupt in
 142 
This variable sets the maximum amount of time to wait for
141 
units of 1us.
 143 
additional packets to arrive (for possible packet coalescing)
142 
The accepted range is 1 to 65535, the default is 100 (100us).
 144 
before firing an Rx completion interrupt, in microseconds.
145 
The accepted range is 1 to 65535; the default is 100 (100us).
143 
.It Va dev.jme.%d.rx_coal_pkt
 146 
.It Va dev.jme.%d.rx_coal_pkt
144 
Maximum number of packets to fire Rx completion interrupt.
 147 
This variable sets the maximum number of incoming packets which may be
145 
The accepted range is 1 to 255, the default is 2.
 148 
coalesced into a single Rx completion interrupt.
149 
The accepted range is 1 to 255; the default is 2.
146 
.It Va dev.jme.%d.process_limit
 150 
.It Va dev.jme.%d.process_limit
147 
Maximum amount of Rx events to be processed in the event loop before
 151 
This variable sets the maximum number of events that will be processed
148 
rescheduling a taskqueue.
 152 
in a single batch before the handler is requeued into a taskqueue.
149 
The accepted range is 10 to 255, the default value is 128 events.
 153 
The accepted range is 10 to 255; the default value is 128 events.
150 
The interface does not need to be brought down and up again before
 154 
The interface does not need to be brought down and up again before
151 
a change takes effect.
 155 
a change takes effect.
152 
.El
 156 
.El
Lines 173-194 Link Here
173 
controllers that use eFuse to store station address.
 177 
controllers that use eFuse to store station address.
174 
The number of times that eFuse can be safely reprogrammed is 16 at
 178 
The number of times that eFuse can be safely reprogrammed is 16 at
175 
most.
 179 
most.
176 
In addition, there is no way to restore factory default station
 180 
In addition, there is no way to restore the factory default station
177 
address once station address is reprogrammed via eFuse.
 181 
address once the station address has been reprogrammed via eFuse.
178 
It is highly recommended not to reprogram station address and
 182 
It is highly recommended not to reprogram the station address and
179 
it is responsibility of administrator to store original station
 183 
it is the responsibility of the administrator to store the original station
180 
address into a safe place when station address should be changed.
 184 
address in a safe place when station address is changed.
181 
.Pp
 185 
.Pp
182 
There are two known 1000baseT link establishment issues with JMC25x.
 186 
There are two known 1000baseT link establishment issues with JMC25x.
183 
If the full mask revision number of JMC25x controller is less than
 187 
If the full mask revision number of JMC25x controller is less than
184 
or equal to 4 and link partner enabled IEEE 802.3az Energy Efficient
 188 
or equal to 4 and the link partner enabled the IEEE 802.3az Energy Efficient
185 
Ethernet feature,  the controller would not be able to establish a
 189 
Ethernet feature,  the controller will not be able to establish a
186 
1000baseT link.
 190 
1000baseT link.
187 
Also if the length of cable is longer than 120 meters, controller
 191 
Also, if the length of the cable is longer than 120 meters, the controller
188 
can not establish a 1000baseT link.
 192 
can not establish a 1000baseT link.
189 
The known workaround for the issue is to force manual link
 193 
The known workaround for these issues is to force manual link
190 
configuration with 100baseTX instead of relying on auto-negotiation.
 194 
configuration with 100baseTX instead of relying on auto-negotiation.
191 
The full mask revision number of controller could be checked with
 195 
The full mask revision number of controller can be checked with the
192 
verbose kernel boot option.
 196 
verbose kernel boot option.
193 
Use lower nibble of chip revision number to get full mask revision of
 197 
Use the lower nibble of the chip revision number to get the
198 
full mask revision of
194 
the controller.
 199 
the controller.

Return to bug 158813