From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Cc: linux@3ware.com
Subject: Re: 3ware 6410 RAID 10 performance?
Date: Fri, 4 May 2001 13:23:26 -0700 [thread overview]
Message-ID: <20010504132326.H6437@work.bitmover.com> (raw)
In-Reply-To: <20010504130103.T22922@work.bitmover.com> <20010504131239.G6437@work.bitmover.com>
In-Reply-To: <20010504131239.G6437@work.bitmover.com>
And yet more data -
Under 2.2.15 using 3ware's driver rather than the one shipped with the
kernel, one complete read goes at 35MB/sec (nice). The second one starts
out there and then drops down to 4MB/sec at the 1.2GB offset.
Here's the cool part - if I unmount, rmmod the driver, insmod, mount, and
then run again, I get exactly the same behavior as above.
This starts to sound like some resource in the kernel or the card are
getting used up and removing the card frees them.
Has anyone seen this besides me?
On Fri, May 04, 2001 at 01:12:39PM -0700, Larry McVoy wrote:
> More data:
>
> the test file is 2GB in size.
> When I do a reboot and time the reading of the entire file,
> the first time the performance is great, 27MB.
> The second time it sucks, 2.7MB.
> I tried clearing memory by allocating and pounding on an array of 512MB
> (size of main mem), that clears out memory but the performance still
> sucks.
> Unmounting and remounting the drive does not help.
>
> Any ideas?
>
> On Fri, May 04, 2001 at 01:01:03PM -0700, Larry McVoy wrote:
> > I'm looking for people who know about the 3ware 6410 driver. I've got one
> > of these and sometimes it goes fast and sometimes it doesn't. The bad
> > case seems to happen after memory has a lot of cached blocks in it.
> >
> > I've tried 2.2.15, 2.4.4, and 2.4.3-ac9 and they all behave pretty similarly.
> >
> > I'm most interested in seeing this fixed in the 2.4 series so if there is
> > someone who wants to go into a test/debug cycle with me, speak up. I'd
> > really like this thing to work well.
> >
> > hardware config:
> >
> > K7 @ 750Mhz
> > ASUS K7V motherboard
> > 512MB
> > 4x 3c905
> > boot disk on the motherboard
> > 4 WD 40GB 7200 drives on one 3ware 6410
> > matrox g200 AGP
> > --
> > ---
> > Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
> > -
> > 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/
>
> --
> ---
> Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
> -
> 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/
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-05-04 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 20:01 3ware 6410 RAID 10 performance? Larry McVoy
2001-05-04 20:12 ` Larry McVoy
2001-05-04 20:23 ` Larry McVoy [this message]
[not found] <53B208BD9A7FD311881A009027B6BBFB9EABAB@siamese>
2001-05-04 21:29 ` Larry McVoy
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=20010504132326.H6437@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@3ware.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