public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: Akinobu Mita <akinobu.mita@gmail.com>, linux-scsi@vger.kernel.org
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 0/7] scsi_debug: several bug fixes and enable clustering support
Date: Sun, 19 Jan 2014 10:59:58 -0500	[thread overview]
Message-ID: <52DBF67E.9030807@interlog.com> (raw)
In-Reply-To: <1390139503-11519-1-git-send-email-akinobu.mita@gmail.com>

On 14-01-19 08:51 AM, Akinobu Mita wrote:
> This patch set includes several bug fixes and patches for enabling
> clustering support for scsi_debug.
>
> The reason why I would like to enable clustering is to test commands
> with huge transfer length.  Without enabling clustering support, the
> transfer length for read and write scsi commands is limited upto 8MB
> when page size is 4KB and sg_tablesize is 2048
> (= SCSI_MAX_SG_CHAIN_SEGMENTS).
>
> Changes from v1:
> - remove unnecessary irqsave/irqrestore while iterating sg mapping
> - protect device access with atomic_rw lock
> - make clustering module parameter writable
>
> Akinobu Mita (7):
>    scsi_debug: fix false positive logical block reference tag check fail
>    scsi_debug: make pseudo_primary static
>    scsi_debug: fix duplicate dif_errors increment
>    scsi_debug: fix resp_xdwriteread() return value when running out of
>      memory
>    scsi_debug: prepare to enable clustering
>    scsi_debug: protect device access with atomic_rw lock
>    scsi_debug: add ability to enable clustering
>
>   drivers/scsi/scsi_debug.c | 141 +++++++++++++++++++++++++++-------------------
>   1 file changed, 82 insertions(+), 59 deletions(-)
>
> Cc: "James E.J. Bottomley" <JBottomley@parallels.com>
> Cc: Douglas Gilbert <dgilbert@interlog.com>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> Cc: linux-scsi@vger.kernel.org

The parts of this patch that I understand look fine. Perhaps
Martin should "ack" it, if he sees fit.

Reviewed-by: Douglas Gilbert <dgilbert@interlog.com>


  parent reply	other threads:[~2014-01-19 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 13:51 [PATCH v2 0/7] scsi_debug: several bug fixes and enable clustering support Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 1/7] scsi_debug: fix false positive logical block reference tag check fail Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 2/7] scsi_debug: make pseudo_primary static Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 3/7] scsi_debug: fix duplicate dif_errors increment Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 4/7] scsi_debug: fix resp_xdwriteread() return value when running out of memory Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 5/7] scsi_debug: prepare to enable clustering Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 6/7] scsi_debug: protect device access with atomic_rw lock Akinobu Mita
2014-01-19 13:51 ` [PATCH v2 7/7] scsi_debug: add ability to enable clustering Akinobu Mita
2014-01-19 15:59 ` Douglas Gilbert [this message]
2014-02-04  4:01   ` [PATCH v2 0/7] scsi_debug: several bug fixes and enable clustering support Martin K. Petersen

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=52DBF67E.9030807@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=JBottomley@parallels.com \
    --cc=akinobu.mita@gmail.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