From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/2] ibmvfc: Delay NPIV login retry and add retries
Date: Wed, 03 Dec 2008 11:38:21 -0600 [thread overview]
Message-ID: <1228325901.5551.31.camel@localhost.localdomain> (raw)
In-Reply-To: <200812031703.mB3H3cMT027696@d03av04.boulder.ibm.com>
On Wed, 2008-12-03 at 11:02 -0600, Brian King wrote:
> Adds a delay prior to retrying a failed NPIV login. This fixes
> a scenario if the backing fibre channel adapter is getting reset
> due to an EEH event, NPIV login will fail. Currently, ibmvfc
> retries three times very quickly, resets the CRQ and tries one
> more time. If the adapter is getting reset due to EEH, this isn't
> enough time. This adds a delay prior to retrying a failed NPIV
> login and also increments the number of retries.
Are these for 2.6.28 or 2.6.29? The descriptions make them sound like
2.6.28 bug fixes.
James
next prev parent reply other threads:[~2008-12-03 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 17:02 [PATCH 1/2] ibmvfc: Delay NPIV login retry and add retries Brian King
2008-12-03 17:38 ` James Bottomley [this message]
2008-12-03 21:54 ` 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=1228325901.5551.31.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=brking@linux.vnet.ibm.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.