From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Tom Yan <tom.ty89@gmail.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, Karel Zak <kzak@redhat.com>,
util-linux@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: optimal io size / custom alignment
Date: Thu, 18 Jun 2015 17:01:19 -0400 [thread overview]
Message-ID: <yq1a8vwenog.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAGnHSEnMgivXU_0gDaOkHFkbc=Ve8PaPR0ho8+VhdcUuNu89Gw@mail.gmail.com> (Tom Yan's message of "Wed, 17 Jun 2015 17:49:51 +0800")
>>>>> "Tom" == Tom Yan <tom.ty89@gmail.com> writes:
Tom> No I put it in the wrong way. What I meant was "sd vs md". For
Tom> example, couldn't the scsi disk driver bind the value it reads from
Tom> the VPD to another variable instead of "optimal i/o size", so that
Tom> this value would be exclusively for RAID (and other virtual
Tom> devices)?
Who says that RAID is a virtual device? Hardware RAID controllers as
well as SAS, iSCSI and Fibre Channel disk arrays all use the Block
Limits VPD to communicate their preferred I/O size and alignment to
us. As do enterprise disk drives.
We deal with broken devices by blacklisting them. I suggest you try to
find a way we can reliably identify your UAS devices. If there is a
common pattern, we can entertain adding a workaround.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2015-06-18 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 14:52 optimal io size / custom alignment Tom Yan
2015-06-15 13:31 ` Karel Zak
2015-06-16 5:20 ` Tom Yan
2015-06-16 5:37 ` Tom Yan
2015-06-16 9:43 ` Karel Zak
2015-06-16 10:22 ` Tom Yan
2015-06-16 17:08 ` Martin K. Petersen
2015-06-16 19:26 ` Tom Yan
2015-06-16 21:28 ` Martin K. Petersen
2015-06-17 9:49 ` Tom Yan
2015-06-18 21:01 ` Martin K. Petersen [this message]
2015-06-20 16:01 ` Tom Yan
2015-06-21 0:12 ` Martin K. Petersen
2015-06-22 14:32 ` Alan Stern
2015-07-12 4:19 ` optimal io size / custom alignment -- caution on custom aligns Linda Walsh
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=yq1a8vwenog.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=kzak@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=tom.ty89@gmail.com \
--cc=util-linux@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