From: Michael Reed <mdr@sgi.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/6] mpt fusion - fibre channel target discovery prematurely terminates
Date: Mon, 22 May 2006 12:31:12 -0500 [thread overview]
Message-ID: <4471F560.8050709@sgi.com> (raw)
In-Reply-To: <1148139217.3529.19.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Thu, 2006-05-18 at 14:59 -0500, Michael Reed wrote:
>> mpt_config() can return EAGAIN. When this happens, fibre channel target
>> discovery can prematurely terminate with fewer than the total number of
>> targets discovered. This patch detects EAGAIN and reschedules the scan
>> work.
>>
>> Generally, this situation only occurs when the lsiutil program is being
>> used to reset the board.
>
> mpt_config() only returns EAGAIN when it's out of message frames. That
> should be a very transient condition, so if this rarely occurs anyway,
> why not just put an msleep(10) on the condition and then retry? It
> would save all the requeue logic.
It's not so transient during reset processing. I've measured 10 to
15 seconds of elapsed time. But, it always eventually succeeds.
Mike
>
> James
>
>
next prev parent reply other threads:[~2006-05-22 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 19:59 [PATCH 1/6] mpt fusion - fibre channel target discovery prematurely terminates Michael Reed
2006-05-20 15:33 ` James Bottomley
2006-05-22 17:31 ` Michael Reed [this message]
2006-05-22 17:34 ` Michael Reed
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 23:41 Moore, Eric
2006-05-22 17:45 Moore, Eric
2006-05-22 17:57 ` James Bottomley
2006-05-22 18:05 ` Michael Reed
2006-05-22 18:15 Moore, Eric
2006-05-22 18:40 ` Michael Reed
2006-05-24 18:48 ` Michael Reed
2006-05-22 23:09 Moore, Eric
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=4471F560.8050709@sgi.com \
--to=mdr@sgi.com \
--cc=James.Bottomley@SteelEye.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.