new silo handling

SCCS-vsn: share/man/man4/man4.vax/dh.4 6.2
SCCS-vsn: share/man/man4/man4.vax/dmf.4 6.4
SCCS-vsn: share/man/man4/man4.vax/dmz.4 6.3
SCCS-vsn: share/man/man4/man4.vax/dz.4 6.2

diff --git a/usr/src/share/man/man4/man4.vax/dh.4 b/usr/src/share/man/man4/man4.vax/dh.4
index a9e187c..789c591 100644 (file)
--- a/usr/src/share/man/man4/man4.vax/dh.4
+++ b/usr/src/share/man/man4/man4.vax/dh.4
@@ -2,7 +2,7 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)dh.4        6.1 (Berkeley) %G%
+.\"    @(#)dh.4        6.2 (Berkeley) %G%

 .\"
 .TH DH 4 ""
 .UC 4
 .\"
 .TH DH 4 ""
 .UC 4


@@ -32,11 +32,15 @@ connected, and that the line should be treated as hard-wired with carrier
 always present.  Thus specifying ``flags 0x0004'' in the specification of dh0
 would cause line ttyh2 to be treated in this way.
 .PP
 always present.  Thus specifying ``flags 0x0004'' in the specification of dh0
 would cause line ttyh2 to be treated in this way.
 .PP

-The dh driver normally uses input silos
-and polls for input at each clock tick (10 milliseconds)
-rather than taking an interrupt on each input character.
+The
+.I dh
+driver monitors the rate of input on each board,
+and switches between the use of character-at-a-time interrupts
+and input silos.
+While the silo is enabled during periods of high-speed input,
+the driver polls for input 30 times per second.

 .SH FILES
 .SH FILES

-/dev/tty[hi][0-9a-f]
+/dev/tty[h-o][0-9a-f]

 .br
 /dev/ttyd[0-9a-f]
 .SH "SEE ALSO"
 .br
 /dev/ttyd[0-9a-f]
 .SH "SEE ALSO"


@@ -51,12 +55,5 @@ It is not serious.
 \fBdh%d: silo overflow\fR.  The character input silo overflowed
 before it could be serviced.  This can happen if a hard error occurs
 when the CPU is running with elevated priority, as the system will
 \fBdh%d: silo overflow\fR.  The character input silo overflowed
 before it could be serviced.  This can happen if a hard error occurs
 when the CPU is running with elevated priority, as the system will

-then print a message on the console with interrupts disabled.  If the
-Berknet
-is running on a
-.I dh
-line at high speed (e.g. 9600 baud), there is only 1/15th of a second of
-buffering capacity in the silo, and overrun is possible.  This may
-cause a few input characters to be lost to users and a network
-packet is likely to be corrupted, but the network will recover.
+then print a message on the console with interrupts disabled.

 It is not serious.
 It is not serious.

diff --git a/usr/src/share/man/man4/man4.vax/dmf.4 b/usr/src/share/man/man4/man4.vax/dmf.4
index 38295d0..78972be 100644 (file)
--- a/usr/src/share/man/man4/man4.vax/dmf.4
+++ b/usr/src/share/man/man4/man4.vax/dmf.4
@@ -2,7 +2,7 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)dmf.4       6.3 (Berkeley) %G%
+.\"    @(#)dmf.4       6.4 (Berkeley) %G%

 .\"
 .TH DMF 4 ""
 .UC 5
 .\"
 .TH DMF 4 ""
 .UC 5


@@ -21,6 +21,9 @@ The first two of these have full modem control.
 The device also provides a line printer port
 similar to the LP-11.
 Other features of the DMF-32 are not supported.
 The device also provides a line printer port
 similar to the LP-11.
 Other features of the DMF-32 are not supported.

+During autoconfiguration, the driver examines the configuration of each DMF-32
+and adjusts the interrupt vectors so that fewer vector locations are used
+if possible.

 .PP
 Each line attached to a DMF-32 serial line port behaves as described
 in
 .PP
 Each line attached to a DMF-32 serial line port behaves as described
 in


@@ -39,11 +42,13 @@ line should be treated as hard-wired with carrier always present.
 Thus specifying ``flags 0x04'' in the specification of 
 .IR dmf 0
 would cause line ttyA2 to be treated in this way.
 Thus specifying ``flags 0x04'' in the specification of 
 .IR dmf 0
 would cause line ttyA2 to be treated in this way.

+Flags should be set for all lines without hardware support for modem control.

 .PP
 The serial line part of the
 .I dmf
 .PP
 The serial line part of the
 .I dmf

-driver normally uses input silos and polls for input at each clock
-tick (10 milliseconds).
+driver normally enables the input silos with a short timeout
+(30 milliseconds); this allows multiple characters to be received
+per interrupt during periods of high-speed input.

 .PP
 A line printer port on
 .I dmf\^n
 .PP
 A line printer port on
 .I dmf\^n


@@ -57,7 +62,7 @@ features of the
 .IR lp (4)
 driver.
 .SH FILES
 .IR lp (4)
 driver.
 .SH FILES

-/dev/tty[A-I][0-7]
+/dev/tty[A-CE-I][0-7]

 .br
 /dev/ttyd[0-7]
 .br
 .br
 /dev/ttyd[0-7]
 .br


@@ -86,3 +91,7 @@ It is not serious.
 One of the unsupported parts of the dmf interrupted; something
 is amiss, check your interrupt vectors for a conflict with another
 device.
 One of the unsupported parts of the dmf interrupted; something
 is amiss, check your interrupt vectors for a conflict with another
 device.

+.SH BUGS
+It should be possible to set the silo timeout with a configuration file option,
+as the value is a trade-off between efficiency and response time for flow
+control and character echo.

diff --git a/usr/src/share/man/man4/man4.vax/dmz.4 b/usr/src/share/man/man4/man4.vax/dmz.4
index a092d99..c27f563 100644 (file)
--- a/usr/src/share/man/man4/man4.vax/dmz.4
+++ b/usr/src/share/man/man4/man4.vax/dmz.4
@@ -2,7 +2,7 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)dmz.4       6.2 (Berkeley) %G%
+.\"    @(#)dmz.4       6.3 (Berkeley) %G%

 .\"
 .TH DMZ 4 "April 7, 1986"
 .UC 5
 .\"
 .TH DMZ 4 "April 7, 1986"
 .UC 5


@@ -42,13 +42,11 @@ to be treated in this way.
 .PP
 The
 .I dmz
 .PP
 The
 .I dmz

-driver normally uses input silos and polls for input at each clock
-tick (10 milliseconds).
-It uses an adaptive algorithm on output
-to decide whether to use programmed I/O or DMA
-based on the amount of data to send.
+driver normally enables the input silos with a short timeout
+(30 milliseconds); this allows multiple characters to be received
+per interrupt during periods of high-speed input.

 .SH FILES
 .SH FILES

-/dev/tty[abc][0-9a-n]
+/dev/tty[abcefg][0-9a-n]

 .SH SEE ALSO
 tty(4)
 .SH DIAGNOSTICS
 .SH SEE ALSO
 tty(4)
 .SH DIAGNOSTICS


@@ -65,3 +63,7 @@ before it could be serviced.  This can happen if a hard error occurs
 when the CPU is running with elevated priority, as the system will
 then print a message on the console with interrupts disabled.
 It is not serious.
 when the CPU is running with elevated priority, as the system will
 then print a message on the console with interrupts disabled.
 It is not serious.

+.SH BUGS
+It should be possible to set the silo timeout with a configuration file option,
+as the value is a trade-off between efficiency and response time for flow
+control and character echo.

diff --git a/usr/src/share/man/man4/man4.vax/dz.4 b/usr/src/share/man/man4/man4.vax/dz.4
index e465710..cba3a1f 100644 (file)
--- a/usr/src/share/man/man4/man4.vax/dz.4
+++ b/usr/src/share/man/man4/man4.vax/dz.4
@@ -2,7 +2,7 @@
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"
 .\" All rights reserved.  The Berkeley software License Agreement
 .\" specifies the terms and conditions for redistribution.
 .\"

-.\"    @(#)dz.4        6.1 (Berkeley) %G%
+.\"    @(#)dz.4        6.2 (Berkeley) %G%

 .\"
 .TH DZ 4 ""
 .UC 4
 .\"
 .TH DZ 4 ""
 .UC 4


@@ -11,9 +11,9 @@ dz \- DZ-11 communications multiplexer
 .SH SYNOPSIS
 .B "device dz0 at uba0 csr 0160100 vector dzrint dzxint"
 .SH DESCRIPTION
 .SH SYNOPSIS
 .B "device dz0 at uba0 csr 0160100 vector dzrint dzxint"
 .SH DESCRIPTION

-A dz-11 provides 8 communication lines with partial modem control,
+A DZ11 provides 8 communication lines with partial modem control,

 adequate for UNIX dialup use.
 adequate for UNIX dialup use.

-Each line attached to the DZ-11 communications multiplexer
+Each line attached to the DZ11 communications multiplexer

 behaves as described in
 .IR tty (4)
 and may be set to run at any of 16 speeds; see
 behaves as described in
 .IR tty (4)
 and may be set to run at any of 16 speeds; see


@@ -27,9 +27,13 @@ connected, and that the line should be treated as hard-wired with carrier
 always present.  Thus specifying ``flags 0x04'' in the specification of dz0
 would cause line tty02 to be treated in this way.
 .PP
 always present.  Thus specifying ``flags 0x04'' in the specification of dz0
 would cause line tty02 to be treated in this way.
 .PP

-The dz driver normally uses its input silos
-and polls for input at each clock tick (10 milliseconds)
-rather than taking an interrupt on each input character.
+The
+.I dz
+driver monitors the rate of input on each board,
+and switches between the use of character-at-a-time interrupts
+and input silos.
+While the silo is enabled during periods of high-speed input,
+the driver polls for input 30 times per second.

 .SH FILES
 /dev/tty[0-9][0-9]
 .br
 .SH FILES
 /dev/tty[0-9][0-9]
 .br


@@ -41,12 +45,5 @@ tty(4)
 \fBdz%d: silo overflow\fR.  The 64 character input silo overflowed
 before it could be serviced.  This can happen if a hard error occurs
 when the CPU is running with elevated priority, as the system will
 \fBdz%d: silo overflow\fR.  The 64 character input silo overflowed
 before it could be serviced.  This can happen if a hard error occurs
 when the CPU is running with elevated priority, as the system will

-then print a message on the console with interrupts disabled.  If the
-Berknet
-is running on a
-.I dz
-line at high speed (e.g. 9600 baud), there is only 1/15th of a second of
-buffering capacity in the silo, and overrun is possible.  This may
-cause a few input characters to be lost to users and a network
-packet is likely to be corrupted, but the network will recover.
+then print a message on the console with interrupts disabled.

 It is not serious.
 It is not serious.