xref: /dragonfly/share/man/man4/ix.4 (revision 0fe46dc6)
1.\" Copyright (c) 2001-2008, Intel Corporation
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions are met:
6.\"
7.\" 1. Redistributions of source code must retain the above copyright notice,
8.\"    this list of conditions and the following disclaimer.
9.\"
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\"
14.\" 3. Neither the name of the Intel Corporation nor the names of its
15.\"    contributors may be used to endorse or promote products derived from
16.\"    this software without specific prior written permission.
17.\"
18.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
19.\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
22.\" LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
23.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
24.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
25.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
26.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
27.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
28.\" POSSIBILITY OF SUCH DAMAGE.
29.\"
30.\" * Other names and brands may be claimed as the property of others.
31.\"
32.\" $FreeBSD: src/share/man/man4/ixgbe.4,v 1.2 2008/06/17 21:14:02 brueffer Exp $
33.\"
34.Dd November 26, 2015
35.Dt IX 4
36.Os
37.Sh NAME
38.Nm ix
39.Nd "Intel(R) 10Gb Ethernet driver"
40.Sh SYNOPSIS
41To compile this driver into the kernel,
42place the following line in your
43kernel configuration file:
44.Bd -ragged -offset indent
45.Cd "device ix"
46.Ed
47.Pp
48Alternatively, to load the driver as a
49module at boot time, place the following line in
50.Xr loader.conf 5 :
51.Bd -literal -offset indent
52if_ix_load="YES"
53.Ed
54.Sh DESCRIPTION
55The
56.Nm
57driver provides support for PCI Express 10Gb Ethernet adapters based on
58the Intel
5982598,
6082599,
61and
62X540
63Ethernet controller chips.
64The
65.Nm
66driver supports:
67.Pp
68.Bl -item -offset indent -compact
69.It
70Transmit/Receive checksum offload for IP/UDP/TCP.
71.\"Jumbo Frames.
72.It
73Interrupt moderation
74.It
75TCP segmentation offload (TSO)
76.It
77Receive side scaling (RSS)
78.It
79Multiple tranmission queues
80.It
81Multiple vector MSI-X
82.It
83VLAN tag stripping and inserting
84.El
85.Pp
86If
87.Xr polling 4
88or MSI-X is used,
89by default,
90the
91.Nm
92driver will try enabling as many reception queues and transmission queues
93as are allowed by the number of CPUs in the system.
94.Pp
95If multiple transmission queues are used,
96the round-robin arbitration is performed among the transmission queues.
97And if both TSO and multiple tranmission queues are used,
98the round-robin arbitration between transmission queues is done at the
99TCP segment boundary after the hardware segmentation is performed.
100.Pp
10182598 supports 16 reception queues and 32 transmission queues.
102MSI-X is not enabled due to hardware errata.
103Under MSI or legacy interrupt mode,
1042 reception queues are enabled for hardware RSS hash
105and only 1 transmission queue is enable.
106.Pp
10782599 and X540 supports 16 reception queues and 64 transmission queues.
108MSI-X is enable by default.
109However,
110due to the number of MSI-X vectors is 64,
111at most 16 reception queues and 32 transmission queues will be enabled
112under MSI-X mode.
113.Pp
114The
115.Nm
116driver supports the following media types:
117.Bl -tag -width ".Cm autoselect"
118.It Cm autoselect
119Enables auto-negotiation for speed and duplex.
120.El
121.Pp
122The
123.Nm
124driver supports the following media options:
125.Bl -tag -width ".Cm forcepause"
126.It Cm rxpause
127Enable flow control PAUSE reception.
128.It Cm txpause
129Enable flow control PAUSE transmission.
130.It Cm forcepause
131Force flow control PAUSE operation as configured by
132.Cm rxpause
133and
134.Cm txpause
135media options.
136.El
137.Pp
138For more information on configuring this device, see
139.Xr ifconfig 8 .
140The
141.Nm
142driver supports
143.Xr polling 4 .
144.Sh HARDWARE
145The
146.Nm
147driver supports Gigabit Ethernet adapters based on the Intel
14882598,
14982599,
150and
151X540
152controller chips:
153.Pp
154.Bl -bullet -compact
155.It
156Intel 82599EB 10 Gigabit Ethernet Controller
157.It
158Intel 82598EB 10 Gigabit Ethernet Controller
159.It
160Intel Ethernet Converged Network Adapter X520-SR1
161.It
162Intel Ethernet Converged Network Adapter X520-SR2
163.It
164Intel Ethernet Converged Network Adapter X520-DA2
165.It
166Intel Ethernet Converged Network Adapter X520-LR1
167.It
168Intel 82599ES 10 Gigabit Ethernet Controller
169.It
170Intel 10 Gigabit AF DA Dual Port Server Adapter
171.It
172Intel 10 Gigabit AT Server Adapter
173.It
174Intel 10 Gigabit AT2 Server Adapter
175.It
176Intel 10 Gigabit CX4 Dual Port Server Adapter
177.It
178Intel 10 Gigabit XF LR Server Adapter
179.It
180Intel 10 Gigabit XF SR Dual Port Server Adapter
181.It
182Intel 10 Gigabit XF SR Server Adapter
183.It
184Intel Ethernet Converged Network Adapter X540-T1
185.It
186Intel Ethernet Converged Network Adapter X540-T2
187.It
188Intel Ethernet Controller X540-AT2
189.It
190Intel 82599EN 10 Gigabit Ethernet Controller
191.It
192Intel Ethernet Converged Network Adapter X520-DA1
193.It
194Intel Ethernet Converged Network Adapter X520-DA4
195.It
196Intel Ethernet Converged Network Adapter X520-QDA1
197.It
198Intel Ethernet Converged Network Adapter X520-T2
199.It
200Intel Ethernet Controller X710-AM2
201.It
202Intel Ethernet Converged Network Adapter X710-DA2
203.It
204Intel Ethernet Converged Network Adapter X710-DA4
205.El
206.Sh TUNABLES
207Tunables can be set at the
208.Xr loader 8
209prompt before booting the kernel or stored in
210.Xr loader.conf 5 .
211.Em Y
212is the device unit number.
213.Bl -tag -width ".Va hw.ixY.unsupported_sfp"
214.It Va hw.ix.rxd Va hw.ixY.rxd
215Number of receive descriptors allocated by the driver.
216The default value is 2048.
217The minimum is 64,
218and the maximum is 4096.
219.It Va hw.ix.txd Va hw.ixY.txd
220Number of transmit descriptors allocated by the driver.
221The default value is 2048.
222The minimum is 64,
223and the maximum is 4096.
224.It Va hw.ix.rxr Va hw.ixY.rxr
225This tunable specifies the number of reception queues could be enabled.
226Maximum allowed value for these tunables is device specific
227and it must be power of 2 aligned.
228Setting these tunables to 0 allows the driver to make
229as many reception queues ready-for-use as allowed by the number of CPUs.
230.It Va hw.ix.txr Va hw.ixY.txr
231This tunable specifies the number of transmission queues could be enabled.
232Maximum allowed value for these tunables is device specific
233and it must be power of 2 aligned.
234Setting these tunables to 0 allows the driver to make
235as many transmission queues ready-for-use as allowed by the number of CPUs.
236.It Va hw.ix.msix.enable Va hw.ixY.msix.enable
237By default,
238the driver will use MSI-X if it is supported.
239This behaviour can be turned off by setting this tunable to 0.
240.It Va hw.ix.msix.agg_rxtx Va hw.ixY.msix.agg_rxtx
241If MSI-X is used,
242the driver aggregates transmission queue and reception queue processing
243by default.
244This behaviour could be turned off by setting this tunable to 0.
245If the number of MSI-X vectors is not enough to
246put transmission queue processing and reception queue processing
247onto independent MSI-X vector,
248then transmission queue and reception queue processing are always
249aggregated.
250.It Va hw.ixY.msix.off
251If MSI-X is used,
252and transmission queue and reception queue processing are aggregated,
253this tunable specifies the leading target CPU for
254transmission and reception queues processing.
255The value specificed must be aligned to the maximum of
256the number of reception queues
257and the number of transmission queues enabled,
258and must be less than the power of 2 number of CPUs.
259.It Va hw.ixY.msix.rxoff
260If MSI-X is used,
261and transmission queue and reception queue processing are not aggregated,
262this tunable specifies the leading target CPU for reception queues processing.
263The value specificed must be aligned to the number of reception queues enabled
264and must be less than the power of 2 number of CPUs.
265.It Va hw.ixY.msix.txoff
266If MSI-X is used,
267and transmission queue and reception queue processing are not aggregated,
268this tunable specifies the leading target CPU
269for transmission queues processing.
270The value specificed must be aligned to
271the number of transmission queues enabled
272and must be less than the power of 2 number of CPUs.
273.It Va hw.ix.msi.enable Va hw.ixY.msi.enable
274If MSI-X is disabled and MSI is supported,
275the driver will use MSI.
276This behavior can be turned off by setting this tunable to 0.
277.It Va hw.ixY.msi.cpu
278If MSI is used,
279it specifies the MSI's target CPU.
280.It Va hw.ixY.npoll.txoff
281This tunable specifies the leading target CPU for
282transmission queue
283.Xr polling 4
284processing.
285The value specificed must be aligned to the number of transmission queues
286enabled and must be less than the power of 2 number of CPUs.
287.It Va hw.ixY.npoll.rxoff
288This tunable specifies the leading target CPU for
289reception queue
290.Xr polling 4
291processing.
292The value specificed must be aligned to the number of reception queues
293enabled and must be less than the power of 2 number of CPUs.
294.It Va hw.ix.unsupported_sfp
295By default,
296this driver does not allow "unsupported" SFP modules.
297This behavior can be changed by setting this tunable to 1.
298.It Va hw.ix.flow_ctrl Va hw.ixY.flow_ctrl
299The default flow control settings.
300Supported values are:
301rxpause (only enable PAUSE reception),
302txpause (only enable PAUSE transmission),
303full (enable PAUSE reception and transmission),
304none (disable flow control PAUSE operation),
305force-rxpause (force PAUSE reception),
306force-txpause (force PAUSE transmission),
307force-full (forcefully enable PAUSE reception and transmission),
308force-none (forcefully disable flow control PAUSE operation).
309Default is full.
310.El
311.Sh MIB Variables
312A number of per-interface variables are implemented in the
313.Va dev.ix. Ns Em Y
314branch of the
315.Xr sysctl 3
316MIB.
317.Bl -tag -width "rxtx_intr_rate"
318.It Va rxr
319Number of reception queues could be enabled (read-only).
320Use the tunable
321.Va hw.ix.rxr
322or
323.Va hw.ixY.rxr
324to configure it.
325.It Va rxr_inuse
326Number of reception queues being used (read-only).
327.It Va txr
328Number of transmission queues could be enabled (read-only).
329Use the tunable
330.Va hw.ix.txr
331or
332.Va hw.ixY.txr
333to configure it.
334.It Va txr_inuse
335Number of transmission queues being used (read-only).
336.It Va rxd
337Number of descriptors per reception queue (read-only).
338Use the tunable
339.Va hw.ix.rxd
340or
341.Va hw.ixY.rxd
342to configure it.
343.It Va txd
344Number of descriptors per transmission queue (read-only).
345Use the tunable
346.Va hw.ix.txd
347or
348.Va hw.ixY.txd
349to configure it.
350.It Va rxtx_intr_rate
351If MSI or legacy interrupt is used,
352this sysctl controls the highest possible frequency
353that interrupt could be generated by the device.
354If MSI-X is used,
355this sysctl controls the highest possible frequency
356that interrupt could be generated by the MSI-X vectors,
357which aggregate transmission queue and reception queue procecssing.
358It is 8000 by default (125us).
359.It Va rx_intr_rate
360If MSI-X is used,
361this sysctl controls the highest possible frequency
362that interrupt could be generated by the MSI-X vectors,
363which only process reception queue.
364It is 8000 by default (125us).
365.It Va tx_intr_rate
366If MSI-X is used,
367this sysctl controls the highest possible frequency
368that interrupt could be generated by the MSI-X vectors,
369which only process transmission queue.
370It is 6000 by default (~150us).
371.It Va sts_intr_rate
372If MSI-X is used,
373this sysctl controls the highest possible frequency
374that interrupt could be generated by the MSI-X vectors,
375which only process chip status changes.
376It is 8000 by default (125us).
377.It Va tx_intr_nsegs
378Transmission interrupt is asked to be generated upon every
379.Va tx_intr_nsegs
380transmission descritors having been setup.
381The default value is 1/16 of the number of transmission descriptors per queue.
382.It Va tx_wreg_nsegs
383The number of transmission descriptors should be setup
384before the hardware register is written.
385Setting this value too high will have negative effect
386on transmission timeliness.
387Setting this value too low will hurt overall transmission performance
388due to the frequent hardware register writing.
389The default value is 8.
390.It Va rx_wreg_nsegs
391The number of reception descriptors should be setup
392before the hardware register is written.
393Setting this value too high will make device drop incoming packets.
394Setting this value too low will hurt overall reception performance
395due to the frequent hardware register writing.
396The default value is 32.
397.It Va npoll_rxoff
398See the tunable
399.Va hw.ixY.npoll.rxoff .
400The set value will take effect the next time
401.Xr polling 4
402is enabled on the device.
403.It Va npoll_txoff
404See the tunable
405.Va hw.ixY.npoll.txoff .
406The set value will take effect the next time
407.Xr polling 4
408is enabled on the device.
409.El
410.Sh SEE ALSO
411.Xr altq 4 ,
412.Xr arp 4 ,
413.Xr ifmedia 4 ,
414.Xr netintro 4 ,
415.Xr ng_ether 4 ,
416.Xr polling 4 ,
417.Xr vlan 4 ,
418.Xr ifconfig 8
419.Sh HISTORY
420The
421.Nm
422device driver first appeared in
423.Dx 3.1 .
424.Sh AUTHORS
425The
426.Nm
427driver was written by
428.An Intel Corporation Aq Mt freebsdnic@mailbox.intel.com .
429