From: "Marinos J. Yannikos" <mjy@geizhals.at>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: gdth / SCSI read performance issues (2.2.19 and 2.4.10)
Date: Thu, 25 Oct 2001 00:55:15 +0200 [thread overview]
Message-ID: <3BD746D3.20700@geizhals.at> (raw)
In-Reply-To: <3BD6B278.3070300@geizhals.at> <3BD6ECE6.8C9435C4@zip.com.au> <3BD729B6.6030902@geizhals.at> <3BD73280.7FC6526D@zip.com.au>
Andrew Morton wrote:
> [...] you can't read files through the filesystem
> at greater than 17? Which filesystem?
ext2 (on which I did a "tune2fs -j", but then I found out that the
kernel apparently doesn't support ext3). But, see below.
> [...] It'd be interesting to test it on the same machine with
> the vendor's drivers and win2k.
Indeed - can't do so, unfortunately. It could also be an issue
with the RAID-5 configuration (block size and arrangement of the
disks in the array could be less than optimal as suggested by
the ICP BIOS), so I'm in touch with the very helpful ICP support
people as well.
> dd if=large_file of=/dev/null bs=4096k
OK, that's quite odd - now I get a reasonable ~55 MB/s whatever I
try (dd, cp), so that must have been my mistake (or due to the
kernel profiling option?).
By the way, I'm having lock-ups with 2.4.13 that I can reproduce
(vi <file on reiserfs partition> ... :q ... "Segmentation fault"
... lock-up - console input still works, but apparently processes
don't get scheduled).
Regards,
Marinos
--
Marinos Yannikos, CEO
Preisvergleich Internet Services AG
Franzensbrückenstraße 8/2/16, A-1020 Wien
Tel./Fax: (+431) 5811609-52/-55
prev parent reply other threads:[~2001-10-24 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 12:22 gdth / SCSI read performance issues (2.2.19 and 2.4.10) Marinos Yannikos
2001-10-24 16:31 ` Andrew Morton
2001-10-24 20:51 ` Marinos J. Yannikos
2001-10-24 21:28 ` Andrew Morton
2001-10-24 22:55 ` Marinos J. Yannikos [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=3BD746D3.20700@geizhals.at \
--to=mjy@geizhals.at \
--cc=akpm@zip.com.au \
--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