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: Sat, 20 Jun 2015 20:12:43 -0400 [thread overview]
Message-ID: <yq1k2ux9ax0.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAGnHSE=DGa24TPox8wp4k264jnXjMOq7kzf-tCRf1eJt9kN0ZQ@mail.gmail.com> (Tom Yan's message of "Sun, 21 Jun 2015 00:01:34 +0800")
>>>>> "Tom" == Tom Yan <tom.ty89@gmail.com> writes:
Tom> I know they all use VPDs, but the main point is whether those
Tom> hardware RAIDs or so are handled by sd_mod, and whether those
Tom> "transfer lengths" info are still important when it's just a simple
Tom> drive. To me they look like to be of different nature.
We don't know whether a discovered device is "a simple drive".
And once again: The whole point of the queue limit is to have an common
abstraction for all block devices.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2015-06-21 0:12 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
2015-06-20 16:01 ` Tom Yan
2015-06-21 0:12 ` Martin K. Petersen [this message]
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=yq1k2ux9ax0.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