From: James Smart <James.Smart@emulex.com>
To: Ren Mingxin <renmx@cn.fujitsu.com>
Cc: <James.Bottomley@HansenPartnership.com>,
<Nagalakshmi.Nandigama@lsi.com>, <Sreekanth.Reddy@lsi.com>,
<michaelc@cs.wisc.edu>, <robert.w.love@intel.com>,
<dgilbert@interlog.com>, <hare@suse.de>, <bprakash@broadcom.com>,
<agk@redhat.com>, <neilb@suse.de>, <gregkh@linuxfoundation.org>,
<axboe@kernel.dk>, <tj@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/5] scsi: Allow fast io fail without waiting through timeout
Date: Mon, 20 May 2013 11:53:58 -0400 [thread overview]
Message-ID: <519A4716.7000001@emulex.com> (raw)
In-Reply-To: <1369034103-31644-1-git-send-email-renmx@cn.fujitsu.com>
Ren,
Based on the discussion recently held at LSF 2013, we are reworking the
error recovery path to address all the issues you are mentioning. That
work contradicts these patches. So for now, these should be held off.
-- james s
On 5/20/2013 3:14 AM, Ren Mingxin wrote:
> When there is a scsi command timed-out or failed, the scsi eh
> tries a thorugh recovery, which is necessary for non-redundant
> systems. However, the thorugh recovery usually takes much time,
> which is not acceptable for misson critical systems. To improve
> this latency, if we are working on a redundant system, we should
> avoid the scsi eh for its long time failing recovery, and quick
> failover to another path.
>
> This set of patches is trying to implement above.
>
> NOTE: the userland tools need to eusure the environment
> restriction, which will be implemented later.
>
> Thanks,
> Ren
>
> Ren Mingxin (5):
> scsi: rename return code FAST_IO_FAIL to FAST_IO
> FC transport: Add interface to specify fast io level for timed-out cmds
> SAS transport: Add interface to specify fast io level for timed-out cmds
> lpfc: Allow fast timed-out io recovery
> mptfusion: Allow fast timed-out io recovery
>
> drivers/message/fusion/mptscsih.c | 29 ++++++++-
> drivers/scsi/lpfc/lpfc_scsi.c | 34 ++++++++++
> drivers/scsi/scsi_error.c | 18 ++---
> drivers/scsi/scsi_sas_internal.h | 4 -
> drivers/scsi/scsi_transport_fc.c | 112 ++++++++++++++++++++++++++++++++++--
> drivers/scsi/scsi_transport_iscsi.c | 6 -
> drivers/scsi/scsi_transport_sas.c | 103 ++++++++++++++++++++++++++++++++-
> include/scsi/scsi.h | 2
> include/scsi/scsi_transport_fc.h | 11 +++
> include/scsi/scsi_transport_sas.h | 8 ++
> 10 files changed, 303 insertions(+), 24 deletions(-)
>
>
next prev parent reply other threads:[~2013-05-20 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 7:14 [PATCH 0/5] scsi: Allow fast io fail without waiting through timeout Ren Mingxin
2013-05-20 7:14 ` [PATCH 1/5] scsi: rename return code FAST_IO_FAIL to FAST_IO Ren Mingxin
2013-05-20 7:15 ` [PATCH 2/5] FC transport: Add interface to specify fast io level for timed-out cmds Ren Mingxin
2013-05-20 7:15 ` [PATCH 3/5] SAS " Ren Mingxin
2013-05-20 7:15 ` [PATCH 4/5] lpfc: Allow fast timed-out io recovery Ren Mingxin
2013-05-20 7:15 ` [PATCH 5/5] mptfusion: " Ren Mingxin
2013-05-20 15:53 ` James Smart [this message]
2013-05-22 7:12 ` [PATCH 0/5] scsi: Allow fast io fail without waiting through timeout Ren Mingxin
2013-05-22 18:04 ` James Smart
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=519A4716.7000001@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=Sreekanth.Reddy@lsi.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=bprakash@broadcom.com \
--cc=dgilbert@interlog.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=neilb@suse.de \
--cc=renmx@cn.fujitsu.com \
--cc=robert.w.love@intel.com \
--cc=tj@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