From: Ben <ben@easynews.com>
To: linux-kernel@vger.kernel.org
Subject: I/O Confirmation/Problem under 2.6/2.4
Date: Wed, 23 Jun 2004 10:49:27 -0700 [thread overview]
Message-ID: <1088012966.1347.28.camel@solaris.skunkware.org> (raw)
Hello,
I need someone to confirm that linux is capable of doing large amounts
of I/O with hardware raid controllers. I have tried 4 raid controllers
(2 of which have been confirmed to have issues with linux... namely Dell
PERC *megaraid* series and an Adaptec card *aacraid*) and have not been
able to obtain more then 60MB/s doing hardware raid 5. The raid cards
I'm testing are quad channel ultra160's with a total of 8 10k 72GB
ultra320 drives (2 per channel) per raid volume... thus I should be able
to do a fairly large amount of I/O (100+MB sequential writes I'd
assume).
I have tried every possible striping configuration a long with multiple
filesystem (ext2/3/xfs) configurations so I do not believe it is an
issue with all 4 cards (I am currently testing a Mylex extremeRaid 2000
and have seen these do much more then 60MB/s in the past on other
platforms).
I've tried tuning elevator settings, read-ahead (in 2.4), and changing
the scheduler under 2.6 between default and deadlock. Is there
something that needs to be done to get linux to do large amounts of
I/O. Do the drivers I'm trying (aacraid, megaraid, DAC960, dpt_i2o)
have performance problems?
Please confirm and if possible provide possible settings needed to get
linux in the mode for high i/o or general places to tune I/O.
Thanks,
Ben
next reply other threads:[~2004-06-23 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 17:49 Ben [this message]
2004-06-23 18:28 ` Mark Watts
2004-06-23 18:48 ` Bernd Eckenfels
2004-06-23 19:43 ` comsatcat
2004-06-23 21:16 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 17:46 Ben
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=1088012966.1347.28.camel@solaris.skunkware.org \
--to=ben@easynews.com \
--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®