public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Chapman <doug.chapman@hp.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi@vger.kernel.org,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: RE: [Bugme-new] [Bug 8426] New: massive slowdown on SCSI CD/DVDdrive connected to mptspi driver
Date: Fri, 04 May 2007 17:56:41 -0400	[thread overview]
Message-ID: <1178315801.27774.15.camel@athlon> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D7070C3C3@NAMAIL4.ad.lsil.com>

On Fri, 2007-05-04 at 14:34 -0600, Moore, Eric wrote:
> On Thursday, May 03, 2007 9:50 PM,  Doug Chapman wrote:
> > 
> > ACK, tested this on my system where I originally found the problem and
> > all is well with this.
> > 
> > Ignore my earlier comment about the original patch adding the new
> > function mptspi_initTarget.  After looking at what is going 
> > on I realize
> > that it didn't add this, it was just renamed from mptscsih_initTarget.
> > 
> 
> Are you still having issues?   I'm not clear with the above ACK email.

I was ACKing Andrew's patch as it fixes the issue for me.  Without the
backup patch it is still broken even in the latest git tree.  (Linus's
tree).

> 
> AFAIK, that patch your refering to which I submitted is only moving
> code, not actually changing any functionality.   If your having a
> problem with speed, then its most likely a domain validation problem.

I agree it looks that way.  In fact it took me longer to narrow this
down because I didn't suspect that patch.  But, I tested this multiple
times backing out just that specific patch and it _does_ make the
difference.  It is rather dramatic, takes about 10 minutes to read a
kernel.rpm file from a DVD (takes 2 to 4 seconds normally).

> In this driver, the domain validation is done from the spi transport
> layer.    When you load the driver, there should be some messages
> displayed along with the inquiry info during device scan, that would
> provide the negotiation rates. Search your /var/log/messages or dmesg.
> You can also look in the SysFS, and all the info is there as well.   If
> your device is host_W:Channel_X:Target_Y:Lun_Z, then you would look in
> /sys/class/spi_transport_targetW:X:Y:Z/ , in this folder will be period.
> The period is found below at the end of the each line in nano seconds
> units.
> 
>         factor:0x08   Ultra320 (160 Mega-transfers / second) (6.25 ns)
>         factor:0x09   Ultra160 ( 80 Mega-transfers / second) (12.5 ns)
>         factor:0x0A   Ultra2   ( 40 Mega-transfers / second) (25 ns)
>         factor:0x0B   Ultra2   ( 40 Mega-transfers / second) (30.3 ns)
>         factor:0x0C   Ultra    ( 20 Mega-transfers / second) (50 ns)
>         factor:0x19   FAST     ( 10 Mega-transfers / second)
>         factor:0x32   SCSI     (  5 Mega-transfers / second)
>         factor:0xFF   5 Mega-trasfers/second and asynchronous
> 

/sys/class/spi_transport/target5:0:2/period is 50 with our without the
patch in question.

> 
> Also, in the mpt fusion, I have some debug you could enable, which will
> dump all the negotiation parameters as they are written and read from
> via the driver.  The spi transport layer calls these entry points when
> it wants to change the negotiation parameter for each test it runs.  In
> the mpt fusion driver Makefile, you need to uncomment the line
> MPT_DEBUG_DV.   When you do that, then mptspi_print_read_nego and
> mptspi_print_write_nego would be called.

Perhaps I can look into this monday.

> 
> I would like to point out that around the same time I supplied that mpt
> fusion patch, there were changes in scsi_transport_spi.c, that would
> effect negotitaion with regards to the starting min sync rate value.
> This file is in /usr/src/linux/drivers/scsi.  You could diff between
> your kernels to see the changes.

I am applying/removing _only_ your patch and the problem goes away with
just removing it.

- Doug



  reply	other threads:[~2007-05-04 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705032226.l43MQfl1029235@fire-2.osdl.org>
2007-05-04  0:20 ` [Bugme-new] [Bug 8426] New: massive slowdown on SCSI CD/DVD drive connected to mptspi driver Andrew Morton
2007-05-04  2:21   ` Doug Chapman
2007-05-04  3:50   ` Doug Chapman
2007-05-04 20:34     ` [Bugme-new] [Bug 8426] New: massive slowdown on SCSI CD/DVDdrive " Moore, Eric
2007-05-04 21:56       ` Doug Chapman [this message]
2007-05-04 22:58         ` James Bottomley
2007-05-07 18:37           ` Doug Chapman
2007-05-07 19:47           ` Doug Chapman

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=1178315801.27774.15.camel@athlon \
    --to=doug.chapman@hp.com \
    --cc=Eric.Moore@lsi.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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