From: James Bottomley <James.Bottomley@SteelEye.com>
To: Ed Lin <ed.lin@promise.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>, jeff <jeff@garzik.org>,
promise_linux <promise_linux@promise.com>
Subject: Re: [PATCH 1/4] stex: fix id mapping issue(v3)
Date: Wed, 04 Apr 2007 20:05:59 -0500 [thread overview]
Message-ID: <1175735159.3693.55.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <NONAMEB8v5DkoQ4qcm500000733@nonameb.ptu.promise.com>
On Wed, 2007-04-04 at 16:56 -0700, Ed Lin wrote:
> The correct internal mapping of stex controllers should be:
> id:0~15, lun:0~7 (st_shasta)
> id:0, lun:0~127 (st_yosemite)
> id:0~127, lun:0 (st_vsc and st_vsc1)
>
> Unfortunately we can not use the internal id/lun as scsi
> mid layer id/lun. The Linux kernel has a config option
> CONFIG_SCSI_MULTI_LUN. This option is not selected
> in some major Linux releases. If it is not selected,
> then st_shasta can expose 16 LDs(logical drive)
> at most, while st_yosemite can expose only one LD.
> This is clearly unacceptable.
Erm, there's a simple way out of this: That's the BLIST_FORCELUN
option. This is why most of the RAID devices have entries in
scsi_devinfo.c like:
{"ADAPTEC", "AACRAID", NULL, BLIST_FORCELUN},
Which overrides the CONFIG_SCSI_MULTI_LUN setting for the particular
device. We can easily add an entry for stex as well.
James
next prev parent reply other threads:[~2007-04-05 1:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 23:56 [PATCH 1/4] stex: fix id mapping issue(v3) Ed Lin
2007-04-05 1:05 ` James Bottomley [this message]
2007-04-05 7:42 ` Christoph Hellwig
2007-04-05 13:58 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2007-04-17 3:46 Ed Lin
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=1175735159.3693.55.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=ed.lin@promise.com \
--cc=jeff@garzik.org \
--cc=linux-scsi@vger.kernel.org \
--cc=promise_linux@promise.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