Cliff White <cliffw@osdl.org> wrote:
>
> The two runs are done like this -> (4 cpu machine)
> ./reaim -s4 -x -t -i4 -f workfile.new_dbase -r3 -b -lstp.config -> for the
> maxjobs convergence
> ./reaim -s4 -q -t -i4 -f workfile.new_dbase -r3 -b -lstp.config -> for the
> 'quick' convergence
>
> stp.config has the poolsizes and path for disk directories:
> FILESIZE 80k
> POOLSIZE 1024k
> DISKDIR /mnt/disk1
> DISKDIR /mnt/disk2
> DISKDIR /mnt/disk3
> DISKDIR /mnt/disk4
Well I spent a few hours running this on the quad xeon (aic7xxx).
There were no hangs, and there was no appreciable performance difference
between 2.5.69, 2.6.69-mm7++ with AS and 2.5.69-mm7++ with deadline.
Please confirm that the hang only happened with the anticipatory scheduler?
It could require a particular device driver to reproduce. Please see if
you can generate that sysrq-T output. Also if you can try a different
device driver sometime that would be interesting. There seem to be several
alternate ISP drivers around - the feral driver perhaps, and the new one in
the linux-scsi tree.
-
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 : Fri May 23 2003 - 22:00:45 EST