From: Ben Collins <bcollins@debian.org>
To: M?ns Rullg?rd <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Firewire/sbp2 troubles with Linux 2.6.0
Date: Sun, 21 Dec 2003 13:31:32 -0500 [thread overview]
Message-ID: <20031221183132.GP6607@phunnypharm.org> (raw)
In-Reply-To: <yw1xn09mkvs9.fsf@ford.guide>
> > I've seen that before with an old card that I had. I was forced to
> > either serialize the serial commands in sbp2, or reduce the max speed to
> > S200.
>
> Setting serialize_io=1 seems to help. I managed to read an 800 MB
> file at 10 MB/s. What's the penalty for setting that? And isn't 10
> MB/s a little slow for Firewire?
Basically that causes the scsi layer to only send sbp2 1 command at a
time, so it's a performance hit.
I'm guessing that your card doesn't like getting some many commands at
once. It's possible that your sbp2 device itself cannot handle it
(generally, I've found it to be caused by the card though).
As far as 10mbs, you have to remember that even though firewire is much
higher than that, your drive is still an IDE, and the firewire is still
going through an IDE bridge. So the limitation lies in the IDE bridge.
I've seen performance as high as 34MB/s with good IDE bridges and
drives, though.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2003-12-21 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 3:26 Firewire/sbp2 troubles with Linux 2.6.0 Måns Rullgård
2003-12-21 3:53 ` Ben Collins
2003-12-21 10:42 ` Måns Rullgård
2003-12-21 14:48 ` Ben Collins
2003-12-21 15:58 ` Måns Rullgård
2003-12-21 18:31 ` Ben Collins [this message]
2003-12-21 19:09 ` Måns Rullgård
2003-12-21 18:48 ` Ben Collins
2003-12-21 19:34 ` Måns Rullgård
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=20031221183132.GP6607@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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