patch-2.3.99-pre6 linux/drivers/scsi/README.st

• Lines: 37
• Date: Mon Apr 24 13:54:22 2000
• Orig file: v2.3.99-pre5/linux/drivers/scsi/README.st
• Orig date: Tue Mar 14 19:10:40 2000

diff -u --recursive --new-file v2.3.99-pre5/linux/drivers/scsi/README.st linux/drivers/scsi/README.st
@@ -2,7 +2,7 @@
 The driver is currently maintained by Kai M{kisara (email
 Kai.Makisara@metla.fi)
 
-Last modified: Sat Mar 11 10:34:44 2000 by makisara@kai.makisara.local
+Last modified: Sat Apr 22 14:50:25 2000 by makisara@kai.makisara.local
 
 
 BASICS
@@ -115,8 +115,8 @@
 at the next tape operation.
 
 Buffered writes and asynchronous writes may in some rare cases cause
-problems in multivolume operations if there is not enough space after
-the early-warning mark to flush the driver buffer.
+problems in multivolume operations if there is not enough space on the
+tape after the early-warning mark to flush the driver buffer.
 
 Read ahead for fixed block mode (ST_READ_AHEAD). Filling the buffer is
 attempted even if the user does not want to get all of the data at
@@ -124,11 +124,11 @@
 a filemark to truncate a read request or that don't like backspacing.
 
 The buffer size is defined (in 1024 byte units) by ST_BUFFER_BLOCKS or
-at boot time. If this size is not enough, the driver tries to allocate
-a large enough temporary buffer that is released when the device is
-closed. Buffer allocation uses chunks of memory having sizes
-2^n * (page size). Because of this the actual buffer size may be
-larger than the buffer size specified with ST_BUFFER_BLOCKS.
+at boot time. If this size is not large enough, the driver tries to
+temporarily enlarge the buffer. Buffer allocation uses chunks of
+memory having sizes 2^n * (page size). Because of this the actual
+buffer size may be larger than the buffer size specified with
+ST_BUFFER_BLOCKS.
 
 A small number of buffers are allocated at driver initialisation. The
 maximum number of these buffers is defined by ST_MAX_BUFFERS. The