From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Doug Ledford <dledford@redhat.com>
Cc: Mark Haverkamp <markh@osdl.org>,
dougg@torque.net, Christoffer Hall-Frederiksen <hall@jiffies.dk>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux aacraid devel <linux-aacraid-devel@dell.com>
Subject: Re: Problem with aacraid driver in 2.5.63-bk-latest
Date: 14 Mar 2003 14:57:59 +0000 [thread overview]
Message-ID: <1047653879.29544.9.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <3E71134F.5060404@redhat.com>
On Thu, 2003-03-13 at 23:25, Doug Ledford wrote:
> Mark Haverkamp wrote:
> > Then it sounds like the aacraid driver could set cmd_per_lun to a small
> > number like one since the real queue depth will be set later in
> > aac_slave_configure.
>
> Yes. And since the driver doesn't support anything other than drives to
> my knowledge, 1 would be appropriate.
It supports both disks and non disk devices. Disks are mapped onto bus 0
and are driven via firmware smarts as logical devices, non disks are bus 1
and there it behaves mostly like a scsi controller
next prev parent reply other threads:[~2003-03-14 13:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030228133037.GB7473@jiffies.dk>
2003-03-12 23:06 ` Mark Haverkamp
2003-03-13 0:18 ` Alan Cox
2003-03-12 23:55 ` Douglas Gilbert
2003-03-13 1:06 ` Alan Cox
2003-03-13 0:50 ` Mike Anderson
2003-03-13 23:13 ` Mark Haverkamp
2003-03-14 7:05 ` Denis Vlasenko
2003-03-14 10:18 ` Mike Anderson
2003-03-13 1:31 ` Douglas Gilbert
2003-03-13 23:27 ` Doug Ledford
2003-03-13 15:42 ` Mark Haverkamp
2003-03-13 23:17 ` Doug Ledford
2003-03-13 23:22 ` Mark Haverkamp
2003-03-13 23:25 ` Doug Ledford
2003-03-14 14:57 ` Alan Cox [this message]
2003-03-14 15:34 ` Mark Haverkamp
2003-03-14 16:48 ` Alan Cox
2003-03-03 10:05 Christoffer Hall-Frederiksen
2003-03-03 13:40 ` Alan Cox
2003-03-03 14:46 ` Christoffer Hall-Frederiksen
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=1047653879.29544.9.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=dledford@redhat.com \
--cc=dougg@torque.net \
--cc=hall@jiffies.dk \
--cc=linux-aacraid-devel@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=markh@osdl.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
all inboxes | Powered by JetHome®