On Wed, Nov 06, 2002 at 10:56:56AM -0500, Adam Kropelin wrote:
> On Wed, Nov 06, 2002 at 08:22:23AM +0100, Jens Axboe wrote:
> > On Tue, Nov 05 2002, Adam Kropelin wrote:
> > > Still without coaster I tried one more thing...
> > > 'dd if=/dev/zero of=foo bs=1M' in parallel with another burn. That one
> > > did it in. ;) I'm running ext3 and the writeout load totally killed
> > > burn, which isn't surprising. I was asking for it, I know. What happened
> >
> > Really, this should work. The deadline scheduler should handle this just
> > fine in fact. Which device is your burner and which device is the hard
> > drive? It sounds like a bug.
>
> Hard disk is sdc on onboard AIC7xxx.
> Writer is hdc, the only device on the secondary onboard IDE channel.
> All other disks (IDE & SCSI) were idle during the test.
What queue depth is the AIC setting?
SCSI in 2.5.x no longer copies the request, so if you have a queue
depth larger than the allocated requests there might not be
any free requests left for the blk layer to play with.
AIC default queue depth is 253 (with 2.5.46 queue depth can be set to 1
if scsi is all in kernel, or no upper drivers are available when the
host adapter is intialized), it should auto lock it to the right depth,
but right now it does not notify the upper layer of the queue depth
change (no call to scsi_adjust_queue_depth when locking in the new
queue depth). You can modify .config, or pass boot/module options to
lower it.
-- Patrick Mansfield
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:44 EST