From: lonely wolf <wolfy@pcnet.ro>
To: linux-kernel@vger.kernel.org
Subject: Re: disk transfer speed problem
Date: Thu, 28 Feb 2002 16:49:25 +0200 [thread overview]
Message-ID: <3C7E4375.50D0789F@pcnet.ro> (raw)
In-Reply-To: <Pine.LNX.4.33.0202281007410.14351-100000@unicef.org.yu>
Davidovac Zoran wrote:
> > -
> on kernel 2.2.20 with andre ata100 patches ported from 2.2.19 to 2.2.20
> on asus i815 board.
> Kernel 2.4.17 results are similar about 35MB/sec
Any chance to get better results with stock kernel 2.4.17 then with 2.4.9-21 (or
-31) ?
I am not in position to do many tests (or reboots for that matter), the machine is
in production, so I'd like a definite approach, if at all possible
next prev parent reply other threads:[~2002-02-28 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0202271701360.13103-100000@coffee.psychology.mcmaster.ca>
2002-02-27 22:52 ` disk transfer speed problem lonely wolf
2002-02-27 23:46 ` Alan Cox
2002-02-28 9:20 ` Davidovac Zoran
2002-02-28 14:49 ` lonely wolf [this message]
2002-03-01 2:25 ` lonely wolf
2002-03-01 10:59 ` Andre Hedrick
2002-03-01 10:51 ` Marco Colombo
2002-02-27 20:49 lonely wolf
2002-02-28 2:06 ` Tim Moore
2002-02-28 4:51 ` Andre Hedrick
2002-02-28 11:56 ` Dave Jones
2002-02-28 17:14 ` Andre Hedrick
2002-02-28 12:27 ` Martin Dalecki
2002-02-28 22:48 ` Stephen Samuel
2002-02-28 23:58 ` lonely wolf
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=3C7E4375.50D0789F@pcnet.ro \
--to=wolfy@pcnet.ro \
--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