From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Desai, Kashyap" <Kashyap.Desai@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Moore, Eric" <Eric.Moore@lsi.com>,
"Prakash, Sathya" <Sathya.Prakash@lsi.com>
Subject: RE: [PATCH 2/6] mpt fusion: Firmware Event implementation using seperate WorkQueue
Date: Tue, 07 Apr 2009 15:46:21 +0000 [thread overview]
Message-ID: <1239119181.9096.21.camel@mulgrave> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C1410F4CC13@inbmail01.lsi.com>
On Tue, 2009-04-07 at 19:18 +0530, Desai, Kashyap wrote:
> It is actually for some customer specific array. They are using multi
> pathing with LSI HBA. When switch over from one path to other path
> happens TUR request for that device won't reply immediately. It
> normally took ~150 seconds.
A multi-pathing fix doesn't belong in your driver. The correct place to
fix this is in the pathing software: if it's dm-mp, it likely needs a
quiesce phase before probing the path.
The reason is that this will manifest for everyone, not just people
using LSI drivers.
James
> Since it is customer specific solution and they are planning to use
> upstream driver in future instead of LSI's inbox driver, I have posted
> it to upstream. Well, I will remove it once that specific need is no
> more required in future.
next prev parent reply other threads:[~2009-04-07 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:50 [PATCH 2/6] mpt fusion: Firmware Event implementation using seperate WorkQueue Kashyap, Desai
2009-04-03 18:21 ` James Bottomley
2009-04-06 8:17 ` Desai, Kashyap
2009-04-06 14:45 ` James Bottomley
2009-04-07 13:48 ` Desai, Kashyap
2009-04-07 15:46 ` James Bottomley [this message]
2009-04-06 8:44 ` Jesper Krogh
2009-04-06 9:06 ` Desai, Kashyap
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=1239119181.9096.21.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=Kashyap.Desai@lsi.com \
--cc=Sathya.Prakash@lsi.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