From: James Bottomley <James.Bottomley@SteelEye.com>
To: Sven Rudolph <Sven_Rudolph@drewag.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Atto UL5D: negotiates only up to FAST-40 SCSI
Date: Fri, 17 Nov 2006 12:26:36 -0600 [thread overview]
Message-ID: <1163787996.8594.36.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <xfkhcwy6la8.fsf@uxrs53.drewag.de>
On Fri, 2006-11-17 at 18:22 +0100, Sven Rudolph wrote:
> Something I forgot to mention: I became aware of the problem when I
> tried to read from (or write to (?)) three disks in parallel and the
> sum of the transfer speeds was a bit below 40 MBytes/second when I ran
> two disks and it was the nearly the same with three disks. The first
> disk was the fastest in the three-disk test run, and the third was the
> slowest. I suppose this is due to SCSI priority by SCSI ID. So I'm
> quite sure that the bus really only runs in FAST-40 mode.
OK ... I think there's something unusual about your actual card. I
checked the specs and FAST-40 should be LVD. The DV information
indicates that the device is also Narrow not wide, which implies either
it refused wide negotiation, or that the card wasn't able to set the
correct parameters. You can try to set it manually with
echo 1 > /sys/class/spi_transport/target1:0:3/width
then you have to do I/O to force the renegotiation (fdisk is good for
this) and then try and cat back the parameter.
You can also try to force it up to FAST-160 with
echo 6.25 > /sys/class/spi_transport/target1:0:3/period
and again force I/O with fdisk then cat the parameter back to see if it
took.
James
next prev parent reply other threads:[~2006-11-17 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 11:21 Atto UL5D: negotiates only up to FAST-40 SCSI Sven Rudolph
2006-11-17 15:31 ` James Bottomley
2006-11-17 16:17 ` Sven Rudolph
2006-11-17 17:22 ` Sven Rudolph
2006-11-17 18:26 ` James Bottomley [this message]
2006-11-17 19:35 ` Sergey Vlasov
2006-11-17 21:15 ` James Bottomley
2006-11-20 14:31 ` Sven Rudolph
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=1163787996.8594.36.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=Sven_Rudolph@drewag.de \
--cc=linux-scsi@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