From: James Bottomley <James.Bottomley@steeleye.com>
To: Brian King <brking@us.ibm.com>
Cc: Martin Peschke3 <MPESCHKE@de.ibm.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Hidden scsi devices
Date: 22 Jan 2004 12:22:38 -0500 [thread overview]
Message-ID: <1074792163.2149.12.camel@mulgrave> (raw)
In-Reply-To: <4010034A.3040903@us.ibm.com>
On Thu, 2004-01-22 at 12:07, Brian King wrote:
> Because the device is reported to the LLDD by the adapter as a
> specific device type. The adapter creates a configuration table
> describing all attached devices that the LLDD must retrieve. In this
> configuration table there are several types of devices:
If you can't ever get access to these devices and you only want sg
access for SCSI command ioctls, you could just alter the device type to
something like PROCESSOR (or even an unclassified type) which will solve
the error messages from sd problem.
The true solution to this issue looks to be more flexibility in the
binding process. We did discuss this previously, certainly in a SAN
environment there are reasons for only actually binding (and allocating
resources to) devices you're interested in.
James
next prev parent reply other threads:[~2004-01-22 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 15:57 [PATCH] Hidden scsi devices Martin Peschke3
2004-01-22 17:07 ` Brian King
2004-01-22 17:22 ` James Bottomley [this message]
2004-01-22 17:33 ` Brian King
2004-01-22 17:50 ` James Bottomley
2004-01-22 18:42 ` Mike Anderson
2004-01-22 19:43 ` Mike Anderson
2004-01-22 19:46 ` James Bottomley
2004-01-22 20:13 ` Brian King
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 15:21 Brian King
2004-01-22 15:50 ` Christoph Hellwig
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=1074792163.2149.12.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=MPESCHKE@de.ibm.com \
--cc=brking@us.ibm.com \
--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