From: Justin Cormack <justin@street-vision.com>
To: Witold Krecicki <adasi@kernel.pl>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [2.4] siimage locks hard on high load
Date: 10 Sep 2003 13:52:38 +0100 [thread overview]
Message-ID: <1063198360.313.54.camel@lotte.street-vision.com> (raw)
In-Reply-To: <200309121344.43573.adasi@kernel.pl>
On Fri, 2003-09-12 at 12:44, Witold Krecicki wrote:
> I've got Asus a7n8x deluxe with on-board Silicon Image SATA and 2xBarracuda
> 120GB connected to it in software RAID array.
> On high disk load (e.g. cp -Rf /usr/src/linux somewhere_else) kernel locks
> hard after about 10 seconds (magic sysrq is not working).
> It happens only when DMA is enabled.
> /dev/hda:
> multcount = 16 (on)
> IO_support = 1 (32-bit)
> unmaskirq = 1 (on)
> using_dma = 1 (on)
> keepsettings = 0 (off)
> readonly = 0 (off)
> readahead = 16 (on)
> geometry = 14593/255/63, sectors = 234441648, start = 0
>
> Also, I'm not really satisfied with speed of this array:
> /dev/md1:
> Timing buffered disk reads: 64 MB in 1.77 seconds = 36.16 MB/sec
> Any solutions/fixes?
Cant help you on the lockups (I havent seen this myself), but the
performance is due to the workaround that sets max_kb_per_request to 15
for siimage. On some drives (Western digital, maxtor) this only cuts the
performance by 10-15MB/s or so but on the Seagates it completely trashes
performance (you can easily test this but you may get data
corruption...).
A proper bug fix rather than a workaround would be nice (unless this
isnt possible). Are the docs for this chipset actually available and is
a bug fix possible? (Alan/Andre should know).
Justin
next prev parent reply other threads:[~2003-09-10 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 11:44 Witold Krecicki
2003-09-10 12:52 ` Justin Cormack [this message]
2003-09-10 13:13 ` Alan Cox
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=1063198360.313.54.camel@lotte.street-vision.com \
--to=justin@street-vision.com \
--cc=adasi@kernel.pl \
--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®