From: Collectively Unconscious <swarm@warpcore.provalue.net>
To: linux-kernel@vger.kernel.org
Subject: I/O problem with sustained writes
Date: Fri, 2 Mar 2001 15:03:30 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.10.10103021455500.29369-100000@warpcore.provalue.net> (raw)
In-Reply-To: <3AA00D5A.44FA21D0@mandrakesoft.com>
We are having a problem with writes.
They start at 14 M/s for the first hour and then drop to 2.5 M/s and stay
that way. Reads do not seem effected and we've noticed this on the 2.2.16,
2.2.17, 2.2.18 and now the 2.2.19pre11 kernels.
These are SMP P-IIIs from 450 to 800 MHz. Redhat 6.2
Jay
next prev parent reply other threads:[~2001-03-02 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-26 10:32 PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-02-26 20:10 ` Jeff Garzik
2001-02-26 20:58 ` Manfred Spraul
2001-03-02 21:15 ` Jeff Garzik
2001-03-02 21:03 ` Collectively Unconscious [this message]
2001-03-02 23:57 ` I/O problem with sustained writes Andrew Morton
2001-03-02 22:20 ` PROBLEM: Network hanging - Tulip driver with Netgear (Lite-On) Manfred Spraul
2001-03-02 22:48 ` Donald Becker
2001-02-27 6:16 ` Pat Verner
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.10.10103021455500.29369-100000@warpcore.provalue.net \
--to=swarm@warpcore.provalue.net \
--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;
as well as URLs for NNTP newsgroup(s).