]> git.ipfire.org Git - thirdparty/man-pages.git/blame_incremental - man4/sk98lin.4
Many pages: Use \[ti] instead of \(ti
[thirdparty/man-pages.git] / man4 / sk98lin.4
... / ...
CommitLineData
1'\" t
2.\" (C)Copyright 1999-2003 Marvell(R) -- linux@syskonnect.de
3.\" sk98lin.4 1.1 2003/12/17 10:03:18
4.\"
5.\" SPDX-License-Identifier: GPL-2.0-or-later
6.\"
7.\" This manpage can be viewed using `groff -Tascii -man sk98lin.4 | less`
8.\"
9.TH sk98lin 4 (date) "Linux man-pages (unreleased)"
10.SH NAME
11sk98lin \- Marvell/SysKonnect Gigabit Ethernet driver v6.21
12.SH SYNOPSIS
13.B insmod sk98lin.o
14.RB [ Speed_A=\c
15.IR i,j,... ]
16.RB [ Speed_B=\c
17.IR i,j,... ]
18.RB [ AutoNeg_A=\c
19.IR i,j,... ]
20.RB [ AutoNeg_B=\c
21.IR i,j,... ]
22.RB [ DupCap_A=\c
23.IR i,j,... ]
24.RB [ DupCap_B=\c
25.IR i,j,... ]
26.RB [ FlowCtrl_A=\c
27.IR i,j,... ]
28.RB [ FlowCtrl_B=\c
29.IR i,j,... ]
30.RB [ Role_A=\c
31.IR i,j,... ]
32.RB [ Role_B=\c
33.IR i,j,... ]
34.RB [ ConType=\c
35.IR i,j,... ]
36.RB [ Moderation=\c
37.IR i,j,... ]
38.RB [ IntsPerSec=\c
39.IR i,j,... ]
40.RB [ PrefPort=\c
41.IR i,j,... ]
42.RB [ RlmtMode=\c
43.IR i,j,... ]
44.SH DESCRIPTION
45.ad l
46.hy 0
47.BR Note :
48This obsolete driver was removed in Linux 2.6.26.
49.PP
50.B sk98lin
51is the Gigabit Ethernet driver for
52Marvell and SysKonnect network adapter cards.
53It supports SysKonnect SK-98xx/SK-95xx
54compliant Gigabit Ethernet Adapter and
55any Yukon compliant chipset.
56.PP
57When loading the driver using insmod,
58parameters for the network adapter cards
59might be stated as a sequence of comma separated commands.
60If for instance two network adapters are installed and AutoNegotiation on
61Port A of the first adapter should be ON,
62but on the Port A of the second adapter switched OFF, one must enter:
63.PP
64.in +4n
65.EX
66insmod sk98lin.o AutoNeg_A=On,Off
67.EE
68.in
69.PP
70After
71.B sk98lin
72is bound to one or more adapter cards and the
73.I /proc
74filesystem is mounted on your system, a dedicated statistics file
75will be created in the folder
76.I /proc/net/sk98lin
77for all ports of the installed network adapter cards.
78Those files are named
79.IR eth[x] ,
80where
81.I x
82is the number of the interface that has been assigned to a
83dedicated port by the system.
84.PP
85If loading is finished, any desired IP address can be
86assigned to the respective
87.I eth[x]
88interface using the
89.BR ifconfig (8)
90command.
91This causes the adapter to connect to the Ethernet and to display a status
92message on the console saying "ethx: network connection up using port y"
93followed by the configured or detected connection parameters.
94.PP
95The
96.B sk98lin
97also supports large frames (also called jumbo frames).
98Using jumbo frames can improve throughput tremendously when
99transferring large amounts of data.
100To enable large frames, the MTU (maximum transfer unit) size
101for an interface is to be set to a high value.
102The default MTU size is 1500 and can be changed up to 9000 (bytes).
103Setting the MTU size can be done when assigning the IP address
104to the interface or later by using the
105.BR ifconfig (8)
106command with the mtu parameter.
107If for instance eth0 needs an IP
108address and a large frame MTU size,
109the following two commands might be used:
110.PP
111.in +4n
112.EX
113ifconfig eth0 10.1.1.1
114ifconfig eth0 mtu 9000
115.EE
116.in
117.PP
118Those two commands might even be combined into one:
119.PP
120.in +4n
121.EX
122ifconfig eth0 10.1.1.1 mtu 9000
123.EE
124.in
125.PP
126Note that large frames can be used only if permitted by
127your network infrastructure.
128This means, that any switch being used in your Ethernet must
129also support large frames.
130Quite some switches support large frames,
131but need to be configured to do so.
132Most of the times, their default setting is to support only
133standard frames with an MTU size of 1500 (bytes).
134In addition to the switches inside the network,
135all network adapters that are to be used must also be
136enabled regarding jumbo frames.
137If an adapter is not set to receive large frames, it will simply drop them.
138.PP
139Switching back to the standard Ethernet frame size can be done by using the
140.BR ifconfig (8)
141command again:
142.PP
143.in +4n
144.EX
145ifconfig eth0 mtu 1500
146.EE
147.in
148.PP
149The Marvell/SysKonnect Gigabit Ethernet driver for Linux is able to
150support VLAN and Link Aggregation according to
151IEEE standards 802.1, 802.1q, and 802.3ad.
152Those features are available only after installation of open source modules
153which can be found on the Internet:
154.PP
155.IR VLAN \c
156:
157.UR http://www.candelatech.com\:/\[ti]greear\:/vlan.html
158.UE
159.br
160.I Link
161.IR Aggregation \c
162:
163.UR http://www.st.rim.or.jp\:/\[ti]yumo
164.UE
165.PP
166Note that Marvell/SysKonnect does not offer any support for these
167open source modules and does not take the responsibility for any
168kind of failures or problems arising when using these modules.
169.SS Parameters
170.TP
171.BI Speed_A= i,j,...
172This parameter is used to set the speed capabilities of port A of an
173adapter card.
174It is valid only for Yukon copper adapters.
175Possible values are:
176.IR 10 ,
177.IR 100 ,
178.IR 1000 ,
179or
180.IR Auto ;
181.I Auto
182is the default.
183Usually, the speed is negotiated between the two ports
184during link establishment.
185If this fails,
186a port can be forced to a specific setting with this parameter.
187.TP
188.BI Speed_B= i,j,...
189This parameter is used to set the speed capabilities of port B of
190an adapter card.
191It is valid only for Yukon copper adapters.
192Possible values are:
193.IR 10 ,
194.IR 100 ,
195.IR 1000 ,
196or
197.IR Auto ;
198.I Auto
199is the default.
200Usually, the speed is negotiated between the two ports during link
201establishment.
202If this fails,
203a port can be forced to a specific setting with this parameter.
204.TP
205.BI AutoNeg_A= i,j,...
206Enables or disables the use of autonegotiation of port A of an adapter card.
207Possible values are:
208.IR On ,
209.IR Off ,
210or
211.IR Sense ;
212.I On
213is the default.
214The
215.I Sense
216mode automatically detects whether the link partner supports
217auto-negotiation or not.
218.TP
219.BI AutoNeg_B= i,j,...
220Enables or disables the use of autonegotiation of port B of an adapter card.
221Possible values are:
222.IR On ,
223.IR Off ,
224or
225.IR Sense ;
226.I On
227is the default.
228The
229.I Sense
230mode automatically detects whether the link partner supports
231auto-negotiation or not.
232.TP
233.BI DupCap_A= i,j,...
234This parameter indicates the duplex mode to be used for port A
235of an adapter card.
236Possible values are:
237.IR Half ,
238.IR Full ,
239or
240.IR Both ;
241.I Both
242is the default.
243This parameter is relevant only if AutoNeg_A of port A is not set to
244.IR Sense .
245If AutoNeg_A is set to
246.IR On ,
247all three values of DupCap_A (
248.IR Half ,
249.IR Full ,
250or
251.IR Both )
252might be stated.
253If AutoNeg_A is set to
254.IR Off ,
255only DupCap_A values
256.I Full
257and
258.I Half
259are allowed.
260This DupCap_A parameter is useful if your link partner does not
261support all possible duplex combinations.
262.TP
263.BI DupCap_B= i,j,...
264This parameter indicates the duplex mode to be used for port B
265of an adapter card.
266Possible values are:
267.IR Half ,
268.IR Full ,
269or
270.IR Both ;
271.I Both
272is the default.
273This parameter is relevant only if AutoNeg_B of port B is not set to
274.IR Sense .
275If AutoNeg_B is set to
276.IR On ,
277all three values of DupCap_B (
278.IR Half ,
279.IR Full ,
280or
281.IR Both )
282might be stated.
283If AutoNeg_B is set to
284.IR Off ,
285only DupCap_B values
286.I Full
287and
288.I Half
289are allowed.
290This DupCap_B parameter is useful if your link partner does not
291support all possible duplex combinations.
292.TP
293.BI FlowCtrl_A= i,j,...
294This parameter can be used to set the flow control capabilities the
295port reports during auto-negotiation.
296Possible values are:
297.IR Sym ,
298.IR SymOrRem ,
299.IR LocSend ,
300or
301.IR None ;
302.I SymOrRem
303is the default.
304The different modes have the following meaning:
305.RS
306.TP
307.IR Sym " = Symmetric"
308Both link partners are allowed to send PAUSE frames.
309.TP
310.IR SymOrRem " = SymmetricOrRemote"
311Both or only remote partner are allowed to send PAUSE frames.
312.TP
313.IR LocSend " = LocalSend"
314Only local link partner is allowed to send PAUSE frames.
315.TP
316.IR None " = None"
317No link partner is allowed to send PAUSE frames.
318.RE
319.IP
320Note that this parameter is ignored if AutoNeg_A is set to
321.IR Off .
322.TP
323.BI FlowCtrl_B= i,j,...
324This parameter can be used to set the flow control capabilities the
325port reports during auto-negotiation.
326Possible values are:
327.IR Sym ,
328.IR SymOrRem ,
329.IR LocSend ,
330or
331.IR None ;
332.I SymOrRem
333is the default.
334The different modes have the following meaning:
335.RS
336.TP
337.IR Sym " = Symmetric"
338Both link partners are allowed to send PAUSE frames.
339.TP
340.IR SymOrRem " = SymmetricOrRemote"
341Both or only remote partner are allowed to send PAUSE frames.
342.TP
343.IR LocSend " = LocalSend"
344Only local link partner is allowed to send PAUSE frames.
345.TP
346.IR None " = None"
347No link partner is allowed to send PAUSE frames.
348.RE
349.IP
350Note that this parameter is ignored if AutoNeg_B is set to
351.IR Off .
352.TP
353.BI Role_A= i,j,...
354This parameter is valid only for 1000Base-T adapter cards.
355For two 1000Base-T ports to communicate,
356one must take the role of the master (providing timing information),
357while the other must be the slave.
358Possible values are:
359.IR Auto ,
360.IR Master ,
361or
362.IR Slave ;
363.I Auto
364is the default.
365Usually, the role of a port is negotiated between two ports during
366link establishment, but if that fails the port A of an adapter card
367can be forced to a specific setting with this parameter.
368.TP
369.BI Role_B= i,j,...
370This parameter is valid only for 1000Base-T adapter cards.
371For two 1000Base-T ports to communicate, one must take
372the role of the master (providing timing information),
373while the other must be the slave.
374Possible values are:
375.IR Auto ,
376.IR Master ,
377or
378.IR Slave ;
379.I Auto
380is the default.
381Usually, the role of a port is negotiated between
382two ports during link establishment, but if that fails
383the port B of an adapter card can be forced to a
384specific setting with this parameter.
385.TP
386.BI ConType= i,j,...
387This parameter is a combination of all five per-port parameters
388within one single parameter.
389This simplifies the configuration of both ports of an adapter card.
390The different values of this variable reflect the
391most meaningful combinations of port parameters.
392Possible values and their corresponding combination of per-port parameters:
393.IP
394.TS
395lb lb lb lb lb lb
396l l l l l l.
397ConType DupCap AutoNeg FlowCtrl Role Speed
398\fIAuto\fP Both On SymOrRem Auto Auto
399\fI100FD\fP Full Off None Auto 100
400\fI100HD\fP Half Off None Auto 100
401\fI10FD\fP Full Off None Auto 10
402\fI10HD\fP Half Off None Auto 10
403.TE
404.IP
405Stating any other port parameter together with this
406.I ConType
407parameter will result in a merged configuration of those settings.
408This is due to
409the fact, that the per-port parameters (e.g.,
410.IR Speed_A )
411have a higher priority than the combined variable
412.IR ConType .
413.TP
414.BI Moderation= i,j,...
415Interrupt moderation is employed to limit the maximum number of interrupts
416the driver has to serve.
417That is, one or more interrupts (which indicate any transmit or
418receive packet to be processed) are queued until the driver processes them.
419When queued interrupts are to be served, is determined by the
420.I IntsPerSec
421parameter, which is explained later below.
422Possible moderation modes are:
423.IR None ,
424.IR Static ,
425or
426.IR Dynamic ;
427.I None
428is the default.
429The different modes have the following meaning:
430.IP
431.I None
432No interrupt moderation is applied on the adapter card.
433Therefore, each transmit or receive interrupt is served immediately
434as soon as it appears on the interrupt line of the adapter card.
435.IP
436.I Static
437Interrupt moderation is applied on the adapter card.
438All transmit and receive interrupts are queued until
439a complete moderation interval ends.
440If such a moderation interval ends, all queued interrupts
441are processed in one big bunch without any delay.
442The term
443.I Static
444reflects the fact, that interrupt moderation is always enabled,
445regardless how much network load is currently passing via a
446particular interface.
447In addition, the duration of the moderation interval has a fixed
448length that never changes while the driver is operational.
449.IP
450.I Dynamic
451Interrupt moderation might be applied on the adapter card,
452depending on the load of the system.
453If the driver detects that the system load is too high,
454the driver tries to shield the system against too much network
455load by enabling interrupt moderation.
456If\[em]at a later time\[em]the CPU utilization decreases
457again (or if the network load is negligible), the interrupt
458moderation will automatically be disabled.
459.IP
460Interrupt moderation should be used when the driver has to
461handle one or more interfaces with a high network load,
462which\[em]as a consequence\[em]leads also to a high CPU utilization.
463When moderation is applied in such high network load situations,
464CPU load might be reduced by 20\[en]30% on slow computers.
465.IP
466Note that the drawback of using interrupt moderation is an increase of
467the round-trip-time (RTT), due to the queuing and serving of
468interrupts at dedicated moderation times.
469.TP
470.BI IntsPerSec= i,j,...
471This parameter determines the length of any interrupt moderation interval.
472Assuming that static interrupt moderation is to be used, an
473.I IntsPerSec
474parameter value of 2000 will lead to an interrupt moderation interval of
475500 microseconds.
476Possible values for this parameter are in the range of
47730...40000 (interrupts per second).
478The default value is 2000.
479.IP
480This parameter is used only if either static or dynamic interrupt moderation
481is enabled on a network adapter card.
482This parameter is ignored if no moderation is applied.
483.IP
484Note that the duration of the moderation interval is to be chosen with care.
485At first glance, selecting a very long duration (e.g., only 100 interrupts per
486second) seems to be meaningful, but the increase of packet-processing delay
487is tremendous.
488On the other hand, selecting a very short moderation time might
489compensate the use of any moderation being applied.
490.TP
491.BI PrefPort= i,j,...
492This parameter is used to force the preferred port to
493A or B (on dual-port network adapters).
494The preferred port is the one that is used if both ports A and B are
495detected as fully functional.
496Possible values are:
497.I A
498or
499.IR B ;
500.I A
501is the default.
502.TP
503.BI RlmtMode= i,j,...
504RLMT monitors the status of the port.
505If the link of the active port fails,
506RLMT switches immediately to the standby link.
507The virtual link is maintained as long as at least one "physical" link is up.
508This parameters states how RLMT should monitor both ports.
509Possible values are:
510.IR CheckLinkState ,
511.IR CheckLocalPort ,
512.IR CheckSeg ,
513or
514.IR DualNet ;
515.I CheckLinkState
516is the default.
517The different modes have the following meaning:
518.IP
519.I CheckLinkState
520Check link state only: RLMT uses the link state reported by the adapter
521hardware for each individual port to determine whether a port can be used
522for all network traffic or not.
523.IP
524.I CheckLocalPort
525In this mode, RLMT monitors the network path between the two
526ports of an adapter by regularly exchanging packets between them.
527This mode requires a network configuration in which the
528two ports are able to "see" each other (i.e., there
529must not be any router between the ports).
530.IP
531.I CheckSeg
532Check local port and segmentation:
533This mode supports the same functions as the CheckLocalPort
534mode and additionally checks network segmentation between the ports.
535Therefore, this mode is to be used only if Gigabit Ethernet
536switches are installed on the network that have been
537configured to use the Spanning Tree protocol.
538.IP
539.I DualNet
540In this mode, ports A and B are used as separate devices.
541If you have a dual port adapter, port A will be configured as
542.I eth[x]
543and port B as
544.IR eth[x+1] .
545Both ports can be used independently with distinct IP addresses.
546The preferred port setting is not used.
547RLMT is turned off.
548.IP
549Note that RLMT modes
550.I CheckLocalPort
551and
552.I CheckLinkState
553are designed to operate in configurations where a
554network path between the ports on one adapter exists.
555Moreover, they are not designed to work where adapters are
556connected back-to-back.
557.SH FILES
558.TP
559.I /proc/net/sk98lin/eth[x]
560The statistics file of a particular interface of an adapter card.
561It contains generic information about the adapter card plus a detailed
562summary of all transmit and receive counters.
563.TP
564.I /usr/src/linux/Documentation/networking/sk98lin.txt
565This is the
566.I README
567file of the
568.I sk98lin
569driver.
570It contains a detailed installation HOWTO and describes all parameters
571of the driver.
572It denotes also common problems and provides the solution to them.
573.SH BUGS
574Report any bugs to linux@syskonnect.de
575.\" .SH AUTHORS
576.\" Ralph Roesler \[em] rroesler@syskonnect.de
577.\" .br
578.\" Mirko Lindner \[em] mlindner@syskonnect.de
579.SH SEE ALSO
580.BR ifconfig (8),
581.BR insmod (8),
582.BR modprobe (8)