From: Roland Dreier <rolandd@cisco.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: I want scsi_target_block() in interrupt context
Date: Wed, 29 Jun 2005 10:52:18 -0700 [thread overview]
Message-ID: <5264vxdp9p.fsf@topspin.com> (raw)
In-Reply-To: <20050629173629.GA32197@infradead.org> (Christoph Hellwig's message of "Wed, 29 Jun 2005 18:36:29 +0100")
Christoph> Just allocate one scsi_host per connection.
OK, that solves the queuing problem nicely.
Right now, I create a scsi_host for each local IB port. For each
scsi_host, I have a writable sysfs attribute that userspace can put
the addresses of remote ports to connect to. Any preference for how
to implement the mechanism for userspace to pass in a remote address
to connect to?
Also, with my current scheme, I have a nice hierarchy of devices from
host port to target port to LUN. Having this topology available seems
nice -- are we losing anything useful for multipathing etc. by not
having a device for the host port?
Thanks,
Roland
next prev parent reply other threads:[~2005-06-29 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 17:27 I want scsi_target_block() in interrupt context Roland Dreier
2005-06-29 17:36 ` Christoph Hellwig
2005-06-29 17:52 ` Roland Dreier [this message]
2005-06-29 20:20 ` Mike Christie
2005-06-29 20:41 ` Roland Dreier
2005-06-29 20:48 ` Mike Christie
2005-06-30 0:01 ` Roland Dreier
2005-07-01 0:24 ` Mike Christie
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=5264vxdp9p.fsf@topspin.com \
--to=rolandd@cisco.com \
--cc=hch@infradead.org \
--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