summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authordd <dd@FreeBSD.org>2001-08-25 21:57:02 +0000
committerdd <dd@FreeBSD.org>2001-08-25 21:57:02 +0000
commit2827f60f4d613fbed40d1a3b1266f4a869ae7af3 (patch)
treee0928a40b1ab8423d43a3e424c5ad7bf33802a95 /share
parent2c3a92a16f2f88937a432173dec7f5760d4f6b34 (diff)
downloadFreeBSD-src-2827f60f4d613fbed40d1a3b1266f4a869ae7af3.zip
FreeBSD-src-2827f60f4d613fbed40d1a3b1266f4a869ae7af3.tar.gz
Revert my queueing -> queuing commit. Both spellings are correct, and
some people prefer the former. Submitted by: ken, nectar
Diffstat (limited to 'share')
-rw-r--r--share/man/man4/adv.42
-rw-r--r--share/man/man4/adw.44
-rw-r--r--share/man/man4/ahb.42
-rw-r--r--share/man/man4/bt.44
-rw-r--r--share/man/man4/netgraph.44
-rw-r--r--share/man/man4/ng_tty.42
6 files changed, 9 insertions, 9 deletions
diff --git a/share/man/man4/adv.4 b/share/man/man4/adv.4
index 6c2476b..50c0c9b 100644
--- a/share/man/man4/adv.4
+++ b/share/man/man4/adv.4
@@ -144,7 +144,7 @@ Per target configuration performed in the
menu, which is accessible at boot,
is honored by this driver.
This includes synchronous/asynchronous transfers,
-maximum synchronous negotiation rate, disconnection, tagged queuing,
+maximum synchronous negotiation rate, disconnection, tagged queueing,
and the host adapter's SCSI ID.
The global setting for the maximum number of tagged transactions allowed
per target is not honored as the CAM SCSI system will automatically determine
diff --git a/share/man/man4/adw.4 b/share/man/man4/adw.4
index a87b574..a42fbf9 100644
--- a/share/man/man4/adw.4
+++ b/share/man/man4/adw.4
@@ -52,7 +52,7 @@ and
.Tn ABP3950U2W .
Both chips support, synchronous transfers
(20MHz and 40MHz max respectively),
-16bit transfers, tagged queuing,
+16bit transfers, tagged queueing,
and up to 253 concurrent SCSI transactions.
.Pp
Per target configuration performed in the
@@ -61,7 +61,7 @@ menu, which is accessible at boot,
is honored by this driver.
This includes synchronous/asynchronous transfers,
maximum synchronous negotiation rate, wide transfers, disconnection,
-tagged queuing, and the host adapter's SCSI ID.
+tagged queueing, and the host adapter's SCSI ID.
The global setting for the maximum number of tagged transactions allowed
per target is not honored as the CAM SCSI system will automatically determine
the maximum number of tags a device can receive as well as guarantee fair
diff --git a/share/man/man4/ahb.4 b/share/man/man4/ahb.4
index 0340c70..b767534 100644
--- a/share/man/man4/ahb.4
+++ b/share/man/man4/ahb.4
@@ -42,7 +42,7 @@ bus connected to an Adaptec
174x hostadapter in
.Dq Em enhanced
mode.
-Tagged queuing and synchronous SCSI transfers are supported.
+Tagged queueing and synchronous SCSI transfers are supported.
.Sh CAVEATS
The Adaptec 174X is very sensitive to SCSI bus termination and cable
length. It may also have difficulties operating with some modern devices
diff --git a/share/man/man4/bt.4 b/share/man/man4/bt.4
index dc19540..cda57c0 100644
--- a/share/man/man4/bt.4
+++ b/share/man/man4/bt.4
@@ -89,12 +89,12 @@ BT-542B ISA 30 SCSI-2 (542B revisions A - G)
AMI FastDisk Host Adapters that are true BusLogic MultiMaster clones are also
supported by this driver.
.Pp
-Tagged queuing is supported on 'W' series adapters, 'C' series adapters
+Tagged queueing is supported on 'W' series adapters, 'C' series adapters
with firmware of rev 4.42 and higher, and 'S' series adapters with firmware
of rev 3.35 and higher.
.Pp
Boards with certain firmware revisions may lock up under heavy load to
-certain devices, especially if tagged queuing is used. Should you encounter
+certain devices, especially if tagged queueing is used. Should you encounter
a problem with your adapter, contact Mylex technical support and ensure you
have the latest firmware for your controller.
.Sh SEE ALSO
diff --git a/share/man/man4/netgraph.4 b/share/man/man4/netgraph.4
index 9030020..d18e9b0 100644
--- a/share/man/man4/netgraph.4
+++ b/share/man/man4/netgraph.4
@@ -273,7 +273,7 @@ utilizes the NETISR system to move message and data delivery to
Nodes that run at other priorities (e.g. interfaces) can be directly
linked to other nodes so that the combination runs at the other priority,
however any interaction with nodes running at splnet MUST be achieved via the
-queuing functions, (which use the
+queueing functions, (which use the
.Fn netisr
feature of the kernel).
Note that messages are always received at
@@ -419,7 +419,7 @@ real data on is passed on, then a
pointer must be substituted. It is also the duty of the receiver to free
the request item itself, or to use it to pass the message on further.
.Pp
-The receiving node may decide to defer the data by queuing it in the
+The receiving node may decide to defer the data by queueing it in the
.Nm
NETISR system (see below). It achieves this by setting the
.Dv HK_QUEUE
diff --git a/share/man/man4/ng_tty.4 b/share/man/man4/ng_tty.4
index 2414e6c..98e3389 100644
--- a/share/man/man4/ng_tty.4
+++ b/share/man/man4/ng_tty.4
@@ -103,7 +103,7 @@ This node type supports the generic control messages, plus the following:
.Bl -tag -width foo
.It Dv NGM_TTY_SET_HOTCHAR
This command takes an integer argument and sets the hot character
-from the lower 8 bits. A hot character of zero disables queuing,
+from the lower 8 bits. A hot character of zero disables queueing,
so that all received data is forwarded immediately.
.It Dv NGM_TTY_GET_HOTCHAR
Returns an integer containing the current hot character in the lower
OpenPOWER on IntegriCloud