public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: azarah@gentoo.org
Cc: Catalin BOIE <util@deuroconsult.ro>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: libata driver update posted
Date: Sat, 19 Jul 2003 16:13:05 -0400	[thread overview]
Message-ID: <3F19A651.2080503@pobox.com> (raw)
In-Reply-To: <1058645294.23174.7.camel@nosferatu.lan>

Martin Schlemmer wrote:
> On Fri, 2003-07-18 at 17:43, Jeff Garzik wrote:
> 
> Slower this side.  The Maxtor 40GB (ata133) is however just set to
> udma33, where the Seagate 20GB (ata100) driver is set correctly to
> udma100.

Yeah, that's expected:  Parallel ATA (PATA) requires cable detection to 
go beyond UDMA/33, and my driver doesn't do that yet [since I'm 
concentrating on SATA].


> The Seagate start off ok (about 35mb/s), but then after doing some heavy
> disk io, it also just drops to the 20mb/s region.

That's definitely interesting.  Is "heavy disk I/O" the hdparm stuff you 
described, or something else too?

	Jeff




  reply	other threads:[~2003-07-19 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 21:14 libata driver update posted Jeff Garzik
2003-07-18  6:24 ` Catalin BOIE
2003-07-18 13:13   ` Jeff Garzik
2003-07-18 15:39     ` Martin Schlemmer
2003-07-18 15:43       ` Jeff Garzik
2003-07-19  0:30         ` Martin Schlemmer
2003-07-19  0:38           ` Alan Cox
2003-07-19  0:52             ` Martin Schlemmer
2003-07-19  0:45           ` Andre Tomt
2003-07-19 20:08         ` Martin Schlemmer
2003-07-19 20:13           ` Jeff Garzik [this message]
2003-07-19 21:18             ` Martin Schlemmer
2003-07-20  2:27             ` James H. Cloos Jr.
2003-07-20  2:51               ` Jeff Garzik

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=3F19A651.2080503@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=azarah@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=util@deuroconsult.ro \
    --cc=vojtech@suse.cz \
    /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