From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-scsi@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] scsi: sd: Optimal I/O size should be a multiple of physical block size
Date: Tue, 19 Jun 2018 21:29:41 -0400 [thread overview]
Message-ID: <yq1lgbafdoa.fsf@oracle.com> (raw)
In-Reply-To: <20180607015123.17862-1-martin.petersen@oracle.com> (Martin K. Petersen's message of "Wed, 6 Jun 2018 21:51:23 -0400")
Christoph,
> It was reported that some devices report an OPTIMAL TRANSFER LENGTH of
> 0xFFFF blocks. That looks bogus, especially for a device with a
> 4096-byte physical block size.
>
> Ignore OPTIMAL TRANSFER LENGTH if it is not a multiple of the device's
> reported physical block size.
Did you get a chance to test the updated patch?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-06-20 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <207561f82d5638c8f513f9aaf970a07098bfbb0f.camel@scientia.net>
2018-06-07 1:51 ` [PATCH] scsi: sd: Optimal I/O size should be a multiple of physical block size Martin K. Petersen
2018-06-20 1:29 ` Martin K. Petersen [this message]
2019-02-08 23:41 Martin K. Petersen
2019-02-12 8:04 ` Christoph Hellwig
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=yq1lgbafdoa.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=calestyo@scientia.net \
--cc=linux-scsi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.