From: Oliver Xymoron <oxymoron@waste.org>
To: Ming Zhang <mingz@ele.uri.edu>
Cc: Doug Ledford <dledford@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Re: about scsi_hostlist
Date: Sun, 17 Nov 2002 23:09:39 -0600 [thread overview]
Message-ID: <20021118050939.GC20171@waste.org> (raw)
In-Reply-To: <200211172237.gAHMbF99022232@leviathan.ele.uri.edu>
On Sun, Nov 17, 2002 at 05:35:52PM -0500, Ming Zhang wrote:
> For example, like the iSCSI target code, when it start, it should
> find all SCSI disks or tapes link in order to export to client side.
No it shouldn't! What if one of them happens to be your boot device?
You'll want to be able to configure from userspace exactly which
devices are available, as well as what authentication they require,
etc.
In fact, I'd recommend running all of the iSCSI target negotiation in
userspace and only push down sockets that have established sessions to the
kernel if you find that you need to for performance. You probably
don't need to.
Further, I'd recommend supporting block devices other than SCSI and
files (similar to the loopback block device) otherwise you're missing
most of the point of using Linux as an iSCSI target. I want to serve
my diskless Beowulf nodes via iSCSI with LVM over RAID5 on IDE disks
and have web manageable storage at a tenth of the cost of SCSI/FC.
Building a cheaper SCSI JBOD is boring.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
next prev parent reply other threads:[~2002-11-18 5:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 22:35 Re: about scsi_hostlist Ming Zhang
2002-11-17 22:41 ` Christoph Hellwig
2002-11-17 22:58 ` Doug Ledford
2002-11-18 5:09 ` Oliver Xymoron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-17 22:43 Ming Zhang
2002-11-17 23:03 Ming Zhang
2002-11-17 23:48 ` Alan Cox
2002-11-18 5:13 ` Oliver Xymoron
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=20021118050939.GC20171@waste.org \
--to=oxymoron@waste.org \
--cc=dledford@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mingz@ele.uri.edu \
/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