From: James Bottomley <James.Bottomley@steeleye.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Mingming Cao <cmm@us.ibm.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.70-mm9
Date: 18 Jun 2003 08:54:44 -0500 [thread overview]
Message-ID: <1055944486.2075.9.camel@mulgrave> (raw)
In-Reply-To: <20030618003838.06144cf9.akpm@digeo.com>
On Wed, 2003-06-18 at 02:38, Andrew Morton wrote:
> Mingming Cao <cmm@us.ibm.com> wrote:
> >
> > I re-run the many fsx tests with feral driver on 2.5.70mm9, ext3
> > fileystems, on deadline scheduler and as scheduler respectively. Both
> > tests passed. They were running for more than 24 hours without any
> > problems. So it could be a bug in the device driver that I used
> > before(QLA2xxx V8). Before the fsx tests failed on ext3 on either
> > deadline scheduler or as scheduler.
>
> Well it could be a bug in the driver, or it could be a bug in the generic
> block/iosched area which was just triggered by the particular way in which
> that driver exercises the core code.
>
> James, do we have the latest-and-greatest version of the qlogic driver
> in-tree? ISTR that there's an update out there somewhere?
I'm still currently keeping the qlogic and feral drivers out of tree.
Feral because Matthew Jacob thinks its not ready yet and Qlogic because
I was waiting for the must-fix list (I'll prod hch again for this).
You can get the current qlogic driver at
http://sourceforge.net/projects/linux-qla2xxx/
And I will update the BK tree at linux-scsi.bkbits.net
James
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2003-06-18 13:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 8:33 2.5.70-mm9 Andrew Morton
2003-06-13 9:17 ` 2.5.70-mm9 Andrew Morton
2003-06-13 10:50 ` Bug in 2.5.70-mm9: df: `/': Value too large for defined data type Thomas Schlichter
2003-06-13 20:09 ` Andrew Morton
2003-06-13 17:57 ` 2.5.70-mm9 Brandon Low
2003-06-14 7:51 ` 2.5.70-mm9 Mingming Cao
2003-06-14 8:01 ` 2.5.70-mm9 Andrew Morton
2003-06-15 0:41 ` 2.5.70-mm9 Mingming Cao
2003-06-15 4:14 ` 2.5.70-mm9 Nick Piggin
2003-06-16 16:25 ` 2.5.70-mm9 Mingming Cao
2003-06-15 6:20 ` 2.5.70-mm9 Andrew Morton
2003-06-16 15:59 ` 2.5.70-mm9 Mingming Cao
2003-06-18 7:13 ` 2.5.70-mm9 Mingming Cao
2003-06-18 7:38 ` 2.5.70-mm9 Andrew Morton
2003-06-18 13:54 ` James Bottomley [this message]
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=1055944486.2075.9.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@digeo.com \
--cc=cmm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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