From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: SCSI LLDs, the SCSI error handler and host resource lifetime
Date: Tue, 27 Nov 2012 16:37:09 +0100 [thread overview]
Message-ID: <50B4DE25.30206@suse.de> (raw)
In-Reply-To: <50B3A59F.3050506@acm.org>
On 11/26/2012 06:23 PM, Bart Van Assche wrote:
> On 11/21/12 08:19, Hannes Reinecke wrote:
>> Hmm.
>> This would still mean that the eh thread will run until finished.
>> Which can take _A LOT_ of time (we're speaking hours here).
>> I would rather have an additional return code in the various
>> scsi_try_XXX functions to terminate the loop quickly.
>
> Hello Hannes,
>
> Since I'm not sure that I understood you properly: is something like
> the patch below what you had in mind ?
>
Yeah, something like this.
Although the usage of 'scsi_host_scan_allowed()' is
non-obvious; after all, we're not _scanning_ this host,
we're just checking if it's working normally.
But thanks for doing this.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-11-27 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 14:24 SCSI LLDs, the SCSI error handler and host resource lifetime Bart Van Assche
2012-11-21 7:19 ` Hannes Reinecke
2012-11-21 12:26 ` Bart Van Assche
2012-11-26 17:23 ` Bart Van Assche
2012-11-27 15:37 ` Hannes Reinecke [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=50B4DE25.30206@suse.de \
--to=hare@suse.de \
--cc=bvanassche@acm.org \
--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.