From: Christoph Hellwig <hch@infradead.org>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] LLDD dynamic scan aids
Date: Thu, 18 Nov 2004 15:43:19 +0000 [thread overview]
Message-ID: <20041118154319.GA24002@infradead.org> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C02F282@xbl3.ma.emulex.com>
> I want to check something: If you truly were probing on a per-port basis, there's no need to ever call scsi_scan_host(), which means there potentially would never be a scan where rescan=0, or that sequential probing of channels/targets occur. Is this an issue ?
Don't think so. Maybe we should allow a !rescan variant of the per-target
probe if you really see performance problems without, but not calling
scsi_scan_host is just fine. In fact that's the reason why I separated
it out from scsi_add_host. The sequential bus scan is fundamentally a SPI
thing and other transports are probably better off not using it at all, e.g.
IEEE1394 SBP2 and iscsi already don't call it at all.
next prev parent reply other threads:[~2004-11-18 15:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 15:32 [PATCH] LLDD dynamic scan aids James.Smart
2004-11-18 15:43 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-29 17:28 Mukker, Atul
2004-11-19 21:07 Mukker, Atul
2004-11-18 15:07 Salyzyn, Mark
2004-11-18 14:32 Salyzyn, Mark
2004-11-18 14:36 ` Christoph Hellwig
2004-11-18 15:48 ` Patrick Mansfield
2004-11-18 14:11 Salyzyn, Mark
2004-11-18 14:26 ` Christoph Hellwig
2004-11-18 13:36 James.Smart
2004-11-18 14:23 ` Christoph Hellwig
2004-11-17 19:03 James.Smart
2004-11-18 10:46 ` 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=20041118154319.GA24002@infradead.org \
--to=hch@infradead.org \
--cc=James.Smart@Emulex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.