From: Florian Hars <hars@bik-gmbh.de>
To: Heinz Diehl <hd@cavy.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disk-I/O and kupdated@99.9% system (2.4.18-pre9)
Date: Mon, 11 Feb 2002 12:55:28 +0100 [thread overview]
Message-ID: <20020211115527.GA336@bik-gmbh.de> (raw)
In-Reply-To: <20020208164250.GA321@bik-gmbh.de> <20020210115509.GA493@chiara.cavy.de>
In-Reply-To: <20020210115509.GA493@chiara.cavy.de>
Heinz Diehl wrote:
> Downgrade to 2.4.18-pre8 and use Michael Cohen's patch from
> "ftp://ftp.kernel.org/pub/linux/kernel/people/mjc/linux-2.4/",
That doesn't help. I tried 2.4.16 with Debian modifications, said
kernel patched to 2.4.18-pre9, stock 2.4.17, stock 2.4.18-pre9 and
2.4.18-pre8-mjc with preempt and lockbreak, and all behave alike.
On a plain ext2-filesystem on a primary partition I get (with -mjc):
During the sync the system is extremly sluggish, and once during my
tests it froze completely (it did still return pings with a normal
speed) so that I had to press reset.
The same operations on a slower computer running 2.2.20 are consideraby
faster:
$ time tar -xzf linux-2.4.17.tar.gz; time sync
real 0m7.716s
user 0m5.430s
sys 0m2.110s
real 0m6.332s
user 0m0.000s
sys 0m0.120s
> Latency in stock 2.4.17/18-pre kernels is well known :\
this looks like more than a latency issue :-(.
Yours, Florian Hars.
next prev parent reply other threads:[~2002-02-11 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 16:42 Disk-I/O and kupdated@99.9% system (2.4.18-pre9) Florian Hars
[not found] ` <20020210115509.GA493@chiara.cavy.de>
2002-02-11 11:55 ` Florian Hars [this message]
2002-02-11 11:59 ` Florian Hars
2002-02-11 19:31 ` Andrew Morton
2002-02-11 19:58 ` 2.5.4 error building vmlinuz Kirk Reiser
2002-02-12 10:20 ` Unknown Southbridge (was: Disk-I/O and kupdated@99.9% system (2.4.18-pre9)) Florian Hars
2002-02-12 10:23 ` Vojtech Pavlik
2002-02-12 13:36 ` Florian Hars
2002-02-12 13:38 ` Vojtech Pavlik
2002-02-13 11:42 ` Florian Hars
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=20020211115527.GA336@bik-gmbh.de \
--to=hars@bik-gmbh.de \
--cc=hd@cavy.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