From: Ric Wheeler <ricwheeler@gmail.com>
To: Hannes Reinecke <hare@suse.de>,
James Bottomley <jbottomley@parallels.com>
Cc: Ren Mingxin <renmx@cn.fujitsu.com>,
emilne@redhat.com, linux-scsi@vger.kernel.org,
Bart van Assche <bvanassche@acm.org>,
Joern Engel <joern@logfs.org>
Subject: Re: [PATCHv2 0/7] Limit overall SCSI EH runtime
Date: Tue, 24 Sep 2013 16:51:58 -0400 [thread overview]
Message-ID: <5241FB6E.6010106@gmail.com> (raw)
In-Reply-To: <521F4768.5010807@suse.de>
On 08/29/2013 09:06 AM, Hannes Reinecke wrote:
> Hi James,
>
> On 08/07/2013 08:43 AM, Ren Mingxin wrote:
>> Hi, James:
>>
>> On 07/11/2013 04:35 AM, Ewan Milne wrote:
>>> Looks good. We have been testing this extensively.
>>>
>>> Acked-by: Ewan D. Milne<emilne@redhat.com>
>> Do you think this patchset can be applied? If so, When? Perhaps you
>> are waiting for someone's feedback?
>>
>> We've also tested and got the duration could be shortened from 6m26s
>> to 44s when 'eh_deadline' was set as 1s(the minimum value of timeout)
>> and 16M data were written(I/O processing time can be ignored - 0.7s).
>>
>> As Ewan said, this is efficient to fast failover policy for redundant
>> environments.
>>
>> Thanks,
>> Ren
> Any objections to this patchset?
> I have other patchsets pending (eg asynchronous command aborts)
> which are based on this one.
> So it would be good to have a status here.
>
> Cheers,
>
> Hannes
Any progress on this patchset? Seems to have gone dormant?
thanks!
Ric
next prev parent reply other threads:[~2013-09-24 20:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 6:50 [PATCHv2 0/7] Limit overall SCSI EH runtime Hannes Reinecke
2013-07-01 6:50 ` [PATCH 1/7] dpt_i2o: Remove DPTI_STATE_IOCTL Hannes Reinecke
2013-07-01 6:50 ` [PATCH 2/7] dpt_i2o: return SCSI_MLQUEUE_HOST_BUSY when in reset Hannes Reinecke
2013-07-01 6:50 ` [PATCH 3/7] advansys: Remove 'last_reset' references Hannes Reinecke
2013-07-01 6:50 ` [PATCH 4/7] tmscsim: Move 'last_reset' into host structure Hannes Reinecke
2013-07-01 6:50 ` [PATCH 5/7] dc395: Move 'last_reset' into internal " Hannes Reinecke
2013-07-01 6:50 ` [PATCH 6/7] scsi: remove check for 'resetting' Hannes Reinecke
2013-07-01 6:50 ` [PATCH 7/7] scsi: Add 'eh_deadline' to limit SCSI EH runtime Hannes Reinecke
2013-09-20 7:48 ` Ren Mingxin
2013-10-16 19:22 ` James Bottomley
2013-10-17 14:27 ` Ewan Milne
2013-10-23 9:25 ` Hannes Reinecke
2013-10-23 7:46 ` James Bottomley
2013-10-23 9:49 ` Hannes Reinecke
2013-07-01 17:44 ` [PATCHv2 0/7] Limit overall " Jörn Engel
2013-07-01 19:23 ` James Bottomley
2013-07-01 20:55 ` Jörn Engel
2013-07-02 5:48 ` Hannes Reinecke
2013-07-02 6:37 ` James Bottomley
2013-07-02 14:58 ` Jörn Engel
2013-07-02 16:33 ` James Bottomley
2013-07-02 15:50 ` Jörn Engel
2013-07-10 20:35 ` Ewan Milne
2013-07-12 5:54 ` Ren Mingxin
2013-07-12 13:30 ` Ewan Milne
2013-07-15 10:33 ` Ren Mingxin
2013-07-26 9:52 ` Ren Mingxin
2013-08-07 6:43 ` Ren Mingxin
2013-08-29 13:06 ` Hannes Reinecke
2013-09-24 20:51 ` Ric Wheeler [this message]
2013-09-25 5:48 ` Hannes Reinecke
2013-10-02 16:21 ` Hannes Reinecke
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=5241FB6E.6010106@gmail.com \
--to=ricwheeler@gmail.com \
--cc=bvanassche@acm.org \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=joern@logfs.org \
--cc=linux-scsi@vger.kernel.org \
--cc=renmx@cn.fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).