From: Andrew Morton <akpm@digeo.com>
To: Cliff White <cliffw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: re-aim - 2.5.69, -mm6
Date: Wed, 21 May 2003 09:25:36 -0700 [thread overview]
Message-ID: <20030521092536.1e04edd1.akpm@digeo.com> (raw)
In-Reply-To: <200305202021.h4KKLUT32174@mail.osdl.org>
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.
next prev parent reply other threads:[~2003-05-21 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 17:43 Cliff White
2003-05-20 19:51 ` Andrew Morton
2003-05-20 20:21 ` Cliff White
2003-05-21 16:25 ` Andrew Morton [this message]
2003-05-21 17:39 ` Cliff White
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030521092536.1e04edd1.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=cliffw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®