From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: James.Smart@Emulex.Com, linux-scsi@vger.kernel.org
Subject: Re: [RFC] adding per scsi-host workqueues for defered processing
Date: Tue, 08 Mar 2005 08:11:36 -0500 [thread overview]
Message-ID: <422DA488.2050007@adaptec.com> (raw)
In-Reply-To: <20050308070010.GE5141@plap.qlogic.org>
On 03/08/05 02:00, Andrew Vasquez wrote:
> There were some background tasks I shelved until the remote-ports
> stuff settled down which I thought could use the deferred processing
> thread:
>
> * Initiate LIP -- several customers have asked for this ability as
> several topological configurations isolate disruptive FC events.
> * Initiate LLDD rescan (i.e. ports (fibre channel), devices (iSCSI),
> etc.)
>
> I had originally envisioned these functions residing in the transport.
Yes, I agree. Domain (target, topology, etc) discovery should be
"part" of the transport class.
What I'm thinking of is that the LLDD would register a known
trasport class with the SCSI Core at/after registering a host
template and then would call something with a name like
"start_scsi" which would do whatever necessary for the domain
(SAS, FC, iSCSI, etc) before scanning for targets. Of course
for some domains no additional work is needed.
Luben
next prev parent reply other threads:[~2005-03-08 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 17:30 [RFC] adding per scsi-host workqueues for defered processing James.Smart
2005-03-08 7:00 ` Andrew Vasquez
2005-03-08 13:11 ` Luben Tuikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 5:19 James.Smart
2005-03-09 7:38 ` Andrew Vasquez
2005-03-09 14:25 ` Brian King
2005-03-05 13:07 James.Smart
2005-03-08 7:10 ` Andrew Vasquez
2005-02-22 4:08 James.Smart
2005-02-22 0:09 Andrew Vasquez
2005-02-22 1:05 ` Matthew Wilcox
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=422DA488.2050007@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=James.Smart@Emulex.Com \
--cc=andrew.vasquez@qlogic.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