From: George Georgalis <george@galis.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Sebastian Slota <SSlota@gmx.net>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops
Date: Fri, 2 Jul 2004 19:01:12 -0400 [thread overview]
Message-ID: <20040702230112.GB27065@trot.local> (raw)
In-Reply-To: <40E25AC1.6030302@pobox.com>
On Wed, Jun 30, 2004 at 02:16:33AM -0400, Jeff Garzik wrote:
>George Georgalis wrote:
>>I was able to dd ~140 GB with SATA_SIL today, on a stock bk kernel, till
>>I ran out of disk, no errors. which was a pleasant unexpected surprise.
>>
>>but when I checked "Timing buffered disk reads" it was around 25 MB/sec
>>not the ~52 MB/sec I saw before with the oops. The odd thing was this
>>disk was not in the blacklist so I don't know why it was running slower.
>
>
>Try mounting a filesystem, unmounting it, and then doing the timing.
With some new (working) ram in the box, and root on hda; sata_sil
gave pretty consistent 29 MB/sec as an auxiliary sda disk, mounted,
remounted, unmounted, verified 29.50 +/- .40 MB/sec, consistently.
However, when I boot with root on sda, I get better performance (?), up
to 41MB/sec and consistently in the 30s; with x and many daemons (but
unloaded)...
Timing buffered disk reads: 100 MB in 3.05 seconds = 32.74 MB/sec
Timing buffered disk reads: 112 MB in 3.04 seconds = 36.84 MB/sec
Timing buffered disk reads: 114 MB in 3.01 seconds = 37.82 MB/sec
Timing buffered disk reads: 104 MB in 3.02 seconds = 34.48 MB/sec
Timing buffered disk reads: 110 MB in 3.00 seconds = 36.64 MB/sec
Timing buffered disk reads: 94 MB in 3.01 seconds = 31.19 MB/sec
Timing buffered disk reads: 88 MB in 3.01 seconds = 29.25 MB/sec
Timing buffered disk reads: 90 MB in 3.06 seconds = 29.37 MB/sec
Timing buffered disk reads: 88 MB in 3.01 seconds = 29.23 MB/sec
Timing buffered disk reads: 108 MB in 3.03 seconds = 35.70 MB/sec
Timing buffered disk reads: 120 MB in 3.04 seconds = 39.47 MB/sec
Timing buffered disk reads: 88 MB in 3.00 seconds = 29.30 MB/sec
(more or less random intervals, at least 5 seconds apart), this
is running a bk kernel checked out June 28. I've written up to 200Gb
to this disk and built a workstation on it, no errors.
Thanks!
// George
--
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@galis.org
Key fingerprint = 5415 2738 61CF 6AE1 E9A7 9EF0 0186 503B 9831 1631
prev parent reply other threads:[~2004-07-02 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040624155919.GA16422@trot.local>
[not found] ` <Pine.GSO.4.33.0406241442430.25702-100000@sweetums.bluetronic.net>
[not found] ` <20040625213433.GB6502@trot.local>
[not found] ` <Pine.LNX.4.58.0406251602140.1844@ppc970.osdl.org>
2004-06-28 2:12 ` SATA_SIL works with 2.6.7-bk8 seagate drive, but oops George Georgalis
[not found] ` <29181.1088498805@www29.gmx.net>
[not found] ` <20040630044352.GB8841@trot.local>
[not found] ` <40E25AC1.6030302@pobox.com>
2004-07-02 23:01 ` George Georgalis [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=20040702230112.GB27065@trot.local \
--to=george@galis.org \
--cc=SSlota@gmx.net \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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).