From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, linuxraid@amcc.com
Subject: Re: [PATCH] 3ware: use scsi_scan_target()
Date: Wed, 05 Oct 2005 15:34:59 -0400 [thread overview]
Message-ID: <43442AE3.6030000@pobox.com> (raw)
In-Reply-To: <20051005162850.GA17710@infradead.org>
Christoph Hellwig wrote:
> On Mon, Oct 03, 2005 at 08:57:46PM -0400, Jeff Garzik wrote:
>
>>This change updates the 3ware raid drivers to use scsi_scan_target(),
>>rather than scsi_scan_host(). This is especially nice for 3w-xxxx,
>>which does not support LUNs. The device scan is a bit quicker and more
>>direct, even if it is a tiny bit more code in the driver.
>
>
> if it doesn't support luns scsi_add_device sounds like the better
> interface to use.
That applies to 3w-xxxx, certainly.
I don't see a strong argument for scsi_add_device() over
scsi_scan_target(), though. scsi_scan_target() directly supports the
generic struct device/class_device stuff, and supports both wildcard LUN
scans as well as no-LUN targets. My vague preference would be to use
scsi_scan_target() unless there is a strong reason not to...
> How does 3x-9xxx support luns? From reading the
> code it doesn't seem to support passthru and faking up LUNs for logical
> volumes sounds odd.
[other emails appear to have addressed this]
Jeff
next prev parent reply other threads:[~2005-10-05 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 0:57 [PATCH] 3ware: use scsi_scan_target() Jeff Garzik
2005-10-05 16:28 ` Christoph Hellwig
2005-10-05 19:01 ` Luben Tuikov
2005-10-05 19:20 ` adam radford
2005-10-05 19:24 ` Jeff Garzik
2005-10-05 19:34 ` Jeff Garzik [this message]
2005-10-05 23:19 ` Luben Tuikov
2005-10-07 1:07 ` James Bottomley
2005-10-07 21:36 ` Luben Tuikov
2005-10-08 14:30 ` James Bottomley
2005-10-09 16:25 ` Luben Tuikov
2005-10-10 5:05 ` Mike Anderson
2005-10-14 16:19 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 13:13 James.Smart
2005-10-06 18:09 ` Luben Tuikov
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=43442AE3.6030000@pobox.com \
--to=jgarzik@pobox.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxraid@amcc.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;
as well as URLs for NNTP newsgroup(s).