From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: suparna@in.ibm.com
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Some interesting results in the aic7xxx slowdown problem
Date: Mon, 29 Aug 2005 10:21:15 -0500 [thread overview]
Message-ID: <1125328875.5089.37.camel@mulgrave> (raw)
In-Reply-To: <20050825103943.GA7421@in.ibm.com>
On Thu, 2005-08-25 at 16:09 +0530, Suparna Bhattacharya wrote:
> On Fri, Aug 19, 2005 at 09:22:45AM -0400, James Bottomley wrote:
> > On Fri, 2005-08-19 at 15:24 +0530, Suparna Bhattacharya wrote:
> > > sda:
> >
> > Well, this line is identifying the root cause. It says that the
> > partition code came up with no partitions for this device. Do any of
> > your other devices come up with paritions? (as in could this be a simple
> > device node transposition issue?)
>
> Yes, it looks like that. The ordering now seems to be id 9, 10, ... 14, 0,
> 1, 2, instead of the default of id 0, 1, 2 ... Did you expect a change
> in probe ordering ?
>
> When I switch back to the old AIC driver the ordering goes back to
> default.
Er, boggle!
I know of no change to the new driver that could affect the target
scanning order (this is target, not lun, right?). Target scan should be
handled sequentially in the mid-layer (scsi_scan.c) in a for loop that
runs from 0 to 15 (well shost->max_id). There is a reverse_order flag,
could that be set somehow?
James
next prev parent reply other threads:[~2005-08-29 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1123119347.5019.78.camel@mulgrave>
[not found] ` <20050804061809.GA4158@in.ibm.com>
[not found] ` <1123166928.5026.8.camel@mulgrave>
2005-08-19 9:54 ` Some interesting results in the aic7xxx slowdown problem Suparna Bhattacharya
2005-08-19 13:22 ` James Bottomley
2005-08-25 10:39 ` Suparna Bhattacharya
2005-08-29 15:21 ` James Bottomley [this message]
2005-08-30 4:49 ` Suparna Bhattacharya
2005-08-30 13:52 ` James Bottomley
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=1125328875.5089.37.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=suparna@in.ibm.com \
/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