From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi_add_host() context
Date: Tue, 19 Nov 2002 00:02:33 +0000 [thread overview]
Message-ID: <20021119000233.A3015@infradead.org> (raw)
In-Reply-To: <3DD841CE.3010309@torque.net>; from dougg@torque.net on Mon, Nov 18, 2002 at 12:26:38PM +1100
On Mon, Nov 18, 2002 at 12:26:38PM +1100, Douglas Gilbert wrote:
> While examining the various calls in the mid level that
> can be called from a LLD, most are designed to
> be called from an interrupt or related context
> (e.g. scsi_adjust_queue_depth() ).
>
> However, the detection of a new host requires a LLD to call
> scsi_register() and scsi_add_host(). The latter call does
> a SCSI bus scan which takes time and sends commands like
> INQUIRY and REPORT_LUNS back through the LLD. So scsi_add_host()
> should not be called from an interrupt context. Can this be
> guaranteed in a hotplug environment? Is a worker thread
> required?
For the driver model ->probe is defined to run in process context, yes.
prev parent reply other threads:[~2002-11-19 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 1:26 scsi_add_host() context Douglas Gilbert
2002-11-19 0:02 ` Christoph Hellwig [this message]
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=20021119000233.A3015@infradead.org \
--to=hch@infradead.org \
--cc=dougg@torque.net \
--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.