From: Douglas Gilbert <dgilbert@interlog.com>
To: linux-scsi@vger.kernel.org
Cc: martin.petersen@oracle.com, jejb@linux.vnet.ibm.com, hare@suse.de
Subject: [RFC v2 0/6] scsi_debug: random doublestore verify
Date: Thu, 9 Jan 2020 09:30:33 +0100 [thread overview]
Message-ID: <20200109083039.16582-1-dgilbert@interlog.com> (raw)
This patchset contains various measures to improve the speed and
usefulness of this driver. It has been used to test the rewrite
of the SCSI generic (sg) driver which is still underway.
Disk to disk copies are the test of choice by the author. Some
testing has been done using real hard disks and SSDs but the
bulk of the testing has been done using this driver as both the
source and destination of the copy. SSDs have two shortcomings:
they are not as fast as the manufacturers would like users to
believe with an average latency to READ at around 100
microseconds; the second problem is "endurance". Endurance is
a wear-out factor based on the number of WRITEs to the SSD.
One would hope both these measures will improve in the future.
The author found that precise command duration timing gave a
false impression of how "bulletproof" the sg driver state
machines and locking was. The first patch involving randomizing
the command durations and it did expose various issues in the
driver under test (sg). The next issue was the correctness of
the bulk copies being done. The doublestore and verify patches
allow the copies to be verified and it demonstrated at least
one area of concern for the sg driver.
Since all scsi_debug memory store accesses are done in the
context of queuecommand() call, the *_irqsave() and
*_irqrestore() variants of the associated locks have been
removed. That could be a problem if queuecommand() can ever
be called form an interrupt or related context.
Finally to address the discrepancy between command duration
times seen by the sg driver compared to what was set with
this driver's ndelay option, this driver's timekeeping for
short durations was made more accurate.
This patchset is against Martin Petersen's git repository
and its 5.6/scsi-queue branch.
Changes since v1:
- testing with version 1 caused several strange crashes that
turned out to be caused by a code trick to read in the
data-out buffer but _not_ place it in the big fake_storep
array. This approach failed badly when multiple threads
were doing verifies at the same time.
- replace the code trick with a new do_dout_fetch() function
- since the code trick was borrowed from the COMPARE AND
WRITE implementation [resp_comp_write()] using
do_dout_fetch() fixes the same bug in the existing driver
which hasn't been reported (yet).
Douglas Gilbert (6):
scsi_debug: randomize command completion time
scsi_debug: add doublestore option
scsi_debug: implement verify(10), add verify(16)
scsi_debug: weaken rwlock around ramdisk access
scsi_debug: improve command duration calculation
scsi_debug: bump to version 1.89
drivers/scsi/scsi_debug.c | 442 +++++++++++++++++++++++++++++---------
1 file changed, 340 insertions(+), 102 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-09 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 8:30 Douglas Gilbert [this message]
2020-01-09 8:30 ` [RFC v2 1/6] scsi_debug: randomize command completion time Douglas Gilbert
2020-01-09 8:30 ` [RFC v2 2/6] scsi_debug: add doublestore option Douglas Gilbert
2020-01-09 8:30 ` [RFC v2 3/6] scsi_debug: implement verify(10), add verify(16) Douglas Gilbert
2020-01-09 8:30 ` [RFC v2 4/6] scsi_debug: weaken rwlock around ramdisk access Douglas Gilbert
2020-01-09 8:30 ` [RFC v2 5/6] scsi_debug: improve command duration calculation Douglas Gilbert
2020-01-09 8:30 ` [RFC v2 6/6] scsi_debug: bump to version 1.89 Douglas Gilbert
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=20200109083039.16582-1-dgilbert@interlog.com \
--to=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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