From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>,
Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] adding per scsi-host workqueues for defered processing
Date: Tue, 22 Feb 2005 01:05:15 +0000 [thread overview]
Message-ID: <20050222010515.GJ28741@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050222000937.GA7338@plap.qlogic.org>
On Mon, Feb 21, 2005 at 04:09:37PM -0800, Andrew Vasquez wrote:
> * must be done from process context -- depending on transport type,
> discovery can occur from a non-process context
> * potentially _long_ scan times -- even if discovery is done from a
> 'sleeping' capable context, halting a LLDD for discovery purposes
> is typically undesirable.
>
> I'd like to propose the addition of a per-Scsi_Host work-queue to
> manage these scanning as well as any other (relevant)
> lower-level-driver differed requests.
Why not use the per-host error handler thread for this?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-02-22 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 0:09 [RFC] adding per scsi-host workqueues for defered processing Andrew Vasquez
2005-02-22 1:05 ` Matthew Wilcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 4:08 James.Smart
2005-03-05 13:07 James.Smart
2005-03-08 7:10 ` Andrew Vasquez
2005-03-05 17:30 James.Smart
2005-03-08 7:00 ` Andrew Vasquez
2005-03-08 13:11 ` Luben Tuikov
2005-03-09 5:19 James.Smart
2005-03-09 7:38 ` Andrew Vasquez
2005-03-09 14:25 ` Brian King
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=20050222010515.GJ28741@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--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