From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, pbadari@us.ibm.com
Subject: Re: 2.5.70-mm6
Date: 12 Jun 2003 11:43:08 -0700 [thread overview]
Message-ID: <1055443389.1518.86.camel@w-ming2.beaverton.ibm.com> (raw)
In-Reply-To: <20030612105041.3e0320a7.akpm@digeo.com>
On Thu, 2003-06-12 at 10:50, Andrew Morton wrote:
> > > Mingming Cao <cmm@us.ibm.com> wrote:
> > Sorry, the tests in 2.5.70 also failed, same problem.
>
> OK. It would be useful to test ext2 as well.
I will try ext2.
> > On Tue, 2003-06-10 at 20:12, Andrew Morton wrote
>
> Everything stuck waiting for IO to complete again.
>
> Are you able to try a different qlogic driver? Or a different HBA?
I will try.
>
> I tried to reproduce this but I don't have sufficient info.
>
Sorry about this.
> How much memory does that machine have, and what fsx-linux command lines
> are you using?
The tests were run on 8 way PIII 700MHZ, with 4G memory. The fsx
command line is:
/root/fsx -R -W -r 4096 -w 4096 /mnt/mntxx/foo &
Thanks for looking at this.
prev parent reply other threads:[~2003-06-12 18:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-07 22:14 2.5.70-mm6 Andrew Morton
2003-06-08 0:37 ` 2.5.70-mm6 Alexander Hoogerhuis
2003-06-08 0:56 ` 2.5.70-mm6 Andrew Morton
2003-06-08 1:13 ` 2.5.70-mm6 Alexander Hoogerhuis
2003-06-08 12:25 ` 2.5.70-mm6 Christoph Hellwig
2003-06-08 12:09 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-08 15:56 ` [patch] 2.5.70-mm6: ethertap.c doesn't compile Adrian Bunk
2003-06-08 16:00 ` Arnaldo Carvalho de Melo
2003-06-08 21:41 ` Adrian Bunk
2003-06-08 22:52 ` 2.5.70-mm6 Pasi Savolainen
2003-06-08 23:17 ` [patch] 2.5.70-mm6: isp driver cleanups Adrian Bunk
2003-06-08 23:27 ` Andrew Morton
2003-06-08 23:24 ` 2.5.70-mm6 Joe
2003-06-09 17:45 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 17:39 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 18:19 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 18:51 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 19:42 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 20:04 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 8:54 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-10 9:20 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:31 ` 2.5.70-mm6 Mike Galbraith
2003-06-10 11:41 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 18:53 ` 2.5.70-mm6 Mike Galbraith
2003-06-10 19:11 ` 2.5.70-mm6 William Lee Irwin III
2003-06-10 11:52 ` 2.5.70-mm6 Maciej Soltysiak
2003-06-09 20:08 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 20:14 ` 2.5.70-mm6 Martin J. Bligh
2003-06-09 21:09 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-10 9:56 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 18:39 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 18:06 ` 2.5.70-mm6 Alistair J Strachan
2003-06-09 18:36 ` 2.5.70-mm6 Felipe Alfaro Solana
2003-06-09 19:07 ` 2.5.70-mm6 Pasi Savolainen
2003-06-09 21:20 ` 2.5.70-mm6 Diego Calleja García
2003-06-09 21:40 ` 2.5.70-mm6 Andrew Morton
2003-06-10 12:10 ` 2.5.70-mm6 Grzegorz Jaskiewicz
2003-06-11 2:15 ` 2.5.70-mm6 Mingming Cao
2003-06-11 3:12 ` 2.5.70-mm6 Andrew Morton
2003-06-11 22:15 ` 2.5.70-mm6 Mingming Cao
2003-06-12 16:37 ` 2.5.70-mm6 Mingming Cao
2003-06-12 17:50 ` 2.5.70-mm6 Andrew Morton
2003-06-12 18:43 ` Mingming Cao [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=1055443389.1518.86.camel@w-ming2.beaverton.ibm.com \
--to=cmm@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).