From: Adam Radford <aradford@3WARE.com>
To: "'raid@ddx.a2000.nu'" <raid@ddx.a2000.nu>
Cc: linux-raid@vger.kernel.org
Subject: RE: 3ware 7500-12, bad write speed
Date: Mon, 14 Oct 2002 11:08:33 -0700 [thread overview]
Message-ID: <A1964EDB64C8094DA12D2271C04B812672C77E@tabby> (raw)
You probably won't get any benefit of 3ware with software raid by
changing max/min readahead, since md.c sets its own readahead.
For the writes, try it and find out.
-Adam
-----Original Message-----
From: raid@ddx.a2000.nu [mailto:raid@ddx.a2000.nu]
Sent: Friday, October 11, 2002 3:05 PM
To: Adam Radford
Cc: linux-raid@vger.kernel.org
Subject: RE: 3ware 7500-12, bad write speed
On Thu, 10 Oct 2002, Adam Radford wrote:
> Can you run the following commands, then re-run your 3ware benchmark and
see
> if the results change?
>
> echo "60" > /proc/sys/vm/bdflush
> echo "512" > /proc/sys/vm/max-readahead
> echo "256" > /proc/sys/vm/min-readahead
Do any of this settings (or any other settings in /proc/sys/vm) help sw
raid ?
also what are the best parameters for mke2fs (both sw and hw raid)
(i now run mke2fs -j -m 0 /dev/sdb1 (or /dev/md0)
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2002-10-14 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 18:08 Adam Radford [this message]
[not found] <A1964EDB64C8094DA12D2271C04B812672C771@tabby>
2002-10-11 22:03 ` 3ware 7500-12, bad write speed raid
2002-10-11 22:05 ` raid
-- strict thread matches above, loose matches on Subject: below --
2002-09-26 17:50 Adam Radford
2002-09-25 21:12 Adam Radford
2002-09-26 5:25 ` Mikael Abrahamsson
2002-09-26 6:04 ` dean gaudet
2002-09-25 20:43 Mikael Abrahamsson
2002-09-26 4:23 ` Maurice Hilarius
2002-09-26 6:43 ` Jason
2002-10-10 21:18 ` raid
2002-10-10 22:27 ` Mikael Abrahamsson
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=A1964EDB64C8094DA12D2271C04B812672C77E@tabby \
--to=aradford@3ware.com \
--cc=linux-raid@vger.kernel.org \
--cc=raid@ddx.a2000.nu \
/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