From: Andrew Patterson <andrew.patterson@hpe.com>
To: Christoph Hellwig <hch@infradead.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] sd: Fix rw_max for devices that report an optimal xfer size
Date: Wed, 1 Jun 2016 15:57:02 -0600 [thread overview]
Message-ID: <574F5A2E.9010000@hpe.com> (raw)
In-Reply-To: <20160601075222.GA3438@infradead.org>
On 06/01/2016 01:52 AM, Christoph Hellwig wrote:
> Looks fine,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> --
> 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
>
I tested this patch on a 3Par array (32K optimal transfer length) that has
issues without this patch. After applying this patch on a linux-stable
kernel, optimal_io_size is correctly reported as 32K.
Tested-by: Andrew Patterson <andrew.patterson@hpe.com>
--
Andrew Patterson
Hewlett-Packard Enterprise
prev parent reply other threads:[~2016-06-01 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1463714194-14258-1-git-send-email-martin.petersen@oracle.com>
2016-06-01 7:52 ` [PATCH] sd: Fix rw_max for devices that report an optimal xfer size Christoph Hellwig
2016-06-01 21:57 ` Andrew Patterson [this message]
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=574F5A2E.9010000@hpe.com \
--to=andrew.patterson@hpe.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.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