From: Hannes Reinecke <hare@suse.de>
To: Ren Mingxin <renmx@cn.fujitsu.com>
Cc: James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org, Joern Engel <joern@logfs.org>,
Ewan Milne <emilne@redhat.com>,
James Smart <james.smart@emulex.com>,
Roland Dreier <roland@purestorage.com>,
Bryn Reeves <bmr@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/4] New SCSI command timeout handler
Date: Fri, 07 Jun 2013 09:31:18 +0200 [thread overview]
Message-ID: <51B18C46.8050205@suse.de> (raw)
In-Reply-To: <51B18398.6000508@cn.fujitsu.com>
On 06/07/2013 08:54 AM, Ren Mingxin wrote:
> Hi, Hannes:
>
> On 06/06/2013 05:43 PM, Hannes Reinecke wrote:
>> this is the first step towards a new non-blocking
>> error handler. This patch implements a new command
>> timeout handler which will be sending command aborts
>> inline without engaging SCSI EH.
>>
>> In addition the commands will be returned directly
>> if the command abort succeeded, cutting down recovery
>> times dramatically.
>>
>> With the original scsi error recovery I got:
>> # time dd if=/dev/zero of=/mnt/test.blk bs=512 count=2048 oflag=sync
>> 2048+0 records in
>> 2048+0 records out
>> 1048576 bytes (1.0 MB) copied, 3.72732 s, 281 kB/s
>>
>> real 2m14.475s
>> user 0m0.000s
>> sys 0m0.104s
>>
>> with this patchset I got:
>> # time dd if=/dev/zero of=/mnt/test.blk bs=512 count=2048 oflag=sync
>> 2048+0 records in
>> 2048+0 records out
>> 1048576 bytes (1.0 MB) copied, 31.5151 s, 33.3 kB/s
>>
>> real 0m31.519s
>> user 0m0.000s
>> sys 0m0.088s
>>
>> Test was to disable RSCN on the target port, disable the
>> target port, and then start the 'dd' command as indicated.
>>
>> As a proof-of-concept I've also enabled the new timeout
>> handler for virtio, so that things can be tested out
>> more easily.
>
> So this 31.5s is tested on virtio disks, right? Much faster than your
> former test via fc.
>
No. This was done on HP Proliant /QLogic FC running against HP P2000.
There is a reason why I posted this new patchset :-)
(The old patchset had a bug where it wouldn't abort the TUR send by
multipaths path-checker. Which were causing delays during
switchover. This version now does terminate them properly)
(Incidentally, it was the non-working scsi_noretry_cmd() which
caused this bug :-)
> This approach may not work for some LLDDs as you said, but I wonder
> whether SAS is applicable(whether there will be later patches for
> SAS).
>
SAS should be applicable for this, too. I'll check.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-06-07 7:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 9:43 [PATCH 0/4] New SCSI command timeout handler Hannes Reinecke
2013-06-06 9:43 ` [PATCH 1/4] scsi: move initialization of scmd->eh_entry Hannes Reinecke
2013-06-06 16:14 ` Jörn Engel
2013-06-06 9:43 ` [PATCH 2/4] blk-timeout: add BLK_EH_SCHEDULED return code Hannes Reinecke
2013-06-06 16:24 ` Jörn Engel
2013-06-06 9:43 ` [PATCH 3/4] scsi: improved eh timeout handler Hannes Reinecke
2013-06-06 16:23 ` Jörn Engel
2013-06-06 20:39 ` Hannes Reinecke
2013-06-06 20:28 ` Jörn Engel
2013-06-07 6:25 ` Ren Mingxin
2013-06-07 6:42 ` Hannes Reinecke
2013-06-07 16:21 ` Jörn Engel
2013-06-10 0:12 ` Baruch Even
2013-06-10 5:48 ` Hannes Reinecke
2013-06-06 9:43 ` [PATCH 4/4] virtio_scsi: use " Hannes Reinecke
2013-06-07 6:54 ` [PATCH 0/4] New SCSI command " Ren Mingxin
2013-06-07 7:31 ` Hannes Reinecke [this message]
2013-06-07 16:02 ` Jörn Engel
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=51B18C46.8050205@suse.de \
--to=hare@suse.de \
--cc=bmr@redhat.com \
--cc=emilne@redhat.com \
--cc=hch@infradead.org \
--cc=james.smart@emulex.com \
--cc=jbottomley@parallels.com \
--cc=joern@logfs.org \
--cc=linux-scsi@vger.kernel.org \
--cc=renmx@cn.fujitsu.com \
--cc=roland@purestorage.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).