From: Con Kolivas <conman@kolivas.net>
To: kernel@mailsammler.de
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Horrible drive performance under concurrent i/o jobs (dlh problem?)
Date: Thu, 19 Dec 2002 08:10:47 +1100 [thread overview]
Message-ID: <1040245847.3e00e457a4d66@kolivas.net> (raw)
>So copied everything away to a software raid and tried all the disk
>tuning stuff (min-, max-readahead, bdflush, elvtune). Nothing helped.
>Last Sunday I then found a hint about a bug introduced in kernel
>2.4.19-pre6 which could be fixed using a "dlh", disk latency hack - or
>going back to 2.4.18. Last is what I did ( from 2.4.20 )
I made the dlh (disk latency hack) and it is related to a problem of system
response under heavy IO load, NOT the actual IO throughput so this sounds
unrelated. However, I have seen what you describe with reiserFS and ide raid at
least and had it fixed by applying AA's stuck in D fix, which ReiserFS is more
prone to for some complicated reason. Give that a go.
In
http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.20aa1/
it is patch 9980_fix-pausing-2
Regards,
Con
next reply other threads:[~2002-12-18 21:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 21:10 Con Kolivas [this message]
2002-12-18 22:16 ` Torben Frey
2002-12-18 22:37 ` Andrew Morton
2002-12-18 23:30 ` Torben Frey
2002-12-18 23:46 ` Andrew Morton
2002-12-18 22:40 ` Torben Frey
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 14:29 Torben Frey
2002-12-20 1:47 ` Nuno Silva
2002-12-27 13:04 ` Torben Frey
2002-12-20 14:27 ` Roger Larsson
2002-12-18 19:06 Torben Frey
2002-12-20 20:40 ` Joseph D. Wagner
2002-12-20 22:25 ` David Lang
2002-12-21 6:00 ` Joseph D. Wagner
2002-12-23 1:29 ` David Lang
2002-12-24 9:18 ` Roy Sigurd Karlsbakk
2002-12-24 17:21 ` jw schultz
2002-12-24 21:00 ` Jeremy Fitzhardinge
2002-12-25 1:34 ` Rik van Riel
2002-12-25 2:02 ` jw schultz
2002-12-25 3:41 ` Barry K. Nathan
2002-12-23 17:48 ` Krzysztof Halasa
2002-12-23 18:13 ` Denis Vlasenko
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=1040245847.3e00e457a4d66@kolivas.net \
--to=conman@kolivas.net \
--cc=kernel@mailsammler.de \
--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
Powered by JetHome