mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Elmer <elmer@linking.ee>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: BUG: softraid,ext3 lockup
Date: Tue, 7 Oct 2003 19:39:02 +0200 (EET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0310071920350.16593-100000@server> (raw)
In-Reply-To: <Pine.LNX.4.44.0310062138350.1556-100000@logos.cnet>



all kernels I have seen are slugish on ide-raid large raw write,

However, now I got some performance test:

dualprocessor server has hda,hdb ibm-hitatchi
	7200 rpm IC35L060AVV207-0, 1860kb cache
uniprocessor  has hda,hdc(was hdb,no diff) western digital
	7200 rpm WDC WD400BB-23DEA0 2000kb cache


Also tested with hdparm -W 1

server      | writeback              |writetrough
------------|------------------------|-----------
dual + ibm: |24 sec,40MB/s,load 1-2  |90 sec 11MB/s,2-4
uni + wdc:  |36 sec,27MB/s,load 1-2  |160 sec 6MB/s,4-7..40


with harddisc writeback the problem does not manifest itself

the problem is present when I do this directly to raw partition /dev/hda2,
(while raid is running on same discs with very slim load and swap being
off, 1GB mem and lots free)

So there are two possible causes now:

1. ServerWorks CSB5 Chipset (rev 93) or driver plus hardiscs
2. Kernel itself, gets too high io performance and everything else is
stuck. So when IO troughput gets a bit higher, the bottleneck goes away.
When some other processes want a little time, they all get very stuck and
load goes to hell.


Elmer.



      reply	other threads:[~2003-10-07 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 13:51 elmer
2003-10-07  0:39 ` Marcelo Tosatti
2003-10-07 17:39   ` Elmer [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=Pine.LNX.4.44.0310071920350.16593-100000@server \
    --to=elmer@linking.ee \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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

all inboxes | Powered by JetHome®