From: Christoph Hellwig <hch@infradead.org>
To: Stefan Voelkel <Stefan.Voelkel@millenux.com>
Cc: Bryan Henderson <hbryan@us.ibm.com>,
Kurt Garloff <garloff@suse.de>,
linux-scsi@vger.kernel.org
Subject: Re: bus:id:lun to device name
Date: Thu, 17 Jul 2003 11:29:51 +0100 [thread overview]
Message-ID: <20030717112951.A18620@infradead.org> (raw)
In-Reply-To: <1058344192.3983.98.camel@lt-sv>; from Stefan.Voelkel@millenux.com on Wed, Jul 16, 2003 at 10:29:52AM +0200
On Wed, Jul 16, 2003 at 10:29:52AM +0200, Stefan Voelkel wrote:
> Yes, basically. I have this information: host_id:bus:target:lun, and now
> I'd like the "device file name with which one normally access' this
> specific lun".
This is not possible in Linux as it's a userspace policy decision.
E.g. scsi cdrom devices at least have three commonly used naming schemes.
> Let me give you some details (hope that will make it clearer). I am
> implementing FC-HBA (ftp://ftp.t11.org/t11/pub/fc/hba/03-108v2.pdf). The
> problem occures with HBA_GetFcpTargetMapping() on page 73 (7.4.4), the
> parameters are describerd on page 31 (6.6.1) and the specific struct is
> HBA_ScsiId (6.6.1.5), actually the member OSDeviceName (6.6.2.11).
This doesn't make any sense in a linux enviroment. I'd rather try to
get that draft fixed before it's ratified instead of working around
it especially as they already mention Linux in some examples.
OTOH it's probably totally irrelevant for real life anyway.
prev parent reply other threads:[~2003-07-17 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 15:24 bus:id:lun to device name Stefan Voelkel
2003-07-08 14:50 ` Kurt Garloff
2003-07-15 14:45 ` Stefan Voelkel
2003-07-15 17:03 ` Bryan Henderson
2003-07-16 8:29 ` Stefan Voelkel
2003-07-17 10:29 ` Christoph Hellwig [this message]
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=20030717112951.A18620@infradead.org \
--to=hch@infradead.org \
--cc=Stefan.Voelkel@millenux.com \
--cc=garloff@suse.de \
--cc=hbryan@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