[376] in linux-scsi channel archive
Re: Reading more than buffersize
daemon@ATHENA.MIT.EDU (Harik A'ttar)
Sat Jul 15 14:29:01 1995
Date: Sat, 15 Jul 1995 10:42:23 -0400 (EDT)
From: "Harik A'ttar" <harik@chaos.sub.ucf.edu>
Reply-To: ind00621@pegasus.cc.ucf.edu
To: Drew Eckhardt <drew@poohsticks.org>
cc: Eric Youngdale <eric@aib.com>,
Christian Ullenboom <ulliull@uni-paderborn.de>,
linux-scsi@vger.rutgers.edu
In-Reply-To: <199507141934.NAA11997@chopper.poohsticks.org>
On Fri, 14 Jul 1995, Drew Eckhardt wrote:
> In message <9507132150.ZM400@aib.com>, eric@aib.com writes:
>
> What really needs to happen is a change in the generic SCSI driver.
>
> Instead of doing things to a buffer and then copying to memory, it should
> lock the relevant pages of user memory in core (there are mlock patches
> floating arround somewhere for this), and do however many SCSI commands are
> necessary (based on the number of scatter/gather segments supported by the
> low level driver being used) to transfer data to those locations.
>
Actually, how much buffering would it take to clean up the choppiness?
I think the problem lies in the way the scanner is being called:
I.E. read 4k at a time, + the scanner delay after every read.
There is probably a better call to the scanner (there must be,
braindead windose uses it) so that it produces smooth, clean scans.
Reply-to should work. Guess what? I really _DO_ speak for my
Dan Merillat / Harik A'ttar system. And if you share my opinions,
in00621@pegasus.cc.ucf.edu you should seek professional help.
