public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Tom Yan <tom.ty89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "Martin K. Petersen"
	<martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Tom Yan's message of "Sun, 21 Jun 2015 00:01:34 +0800")

>>>>> "Tom" == Tom Yan <tom.ty89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in

  parent reply	other threads:[~2015-06-21  0:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGnHSE=gtd2WVcxOBoyfqnp3QtT4RHfK356GHastBbiK5mtmFA@mail.gmail.com>
     [not found] ` <20150615133154.GV1992@ws.net.home>
     [not found]   ` <CAGnHSEm6wDq_EjJXYwqV2Tt2868DbR0bNRYvevhN1AM4qJpaPw@mail.gmail.com>
     [not found]     ` <20150616094320.GX1992@ws.net.home>
     [not found]       ` <20150616094320.GX1992-xkT7n84Rsxv/9pzu0YdTqQ@public.gmane.org>
2015-06-16 10:22         ` optimal io size / custom alignment Tom Yan
     [not found]     ` <yq1zj3zfuna.fsf@sermon.lab.mkp.net>
     [not found]       ` <yq1zj3zfuna.fsf-+q57XtR/GgMb6DWv4sQWN6xOck334EZe@public.gmane.org>
2015-06-16 19:26         ` Tom Yan
2015-06-16 21:28           ` Martin K. Petersen
     [not found]             ` <yq1d20vfimj.fsf-+q57XtR/GgMb6DWv4sQWN6xOck334EZe@public.gmane.org>
2015-06-17  9:49               ` Tom Yan
     [not found]                 ` <CAGnHSEnMgivXU_0gDaOkHFkbc=Ve8PaPR0ho8+VhdcUuNu89Gw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-18 21:01                   ` Martin K. Petersen
     [not found]                     ` <yq1a8vwenog.fsf-+q57XtR/GgMb6DWv4sQWN6xOck334EZe@public.gmane.org>
2015-06-20 16:01                       ` Tom Yan
     [not found]                         ` <CAGnHSE=DGa24TPox8wp4k264jnXjMOq7kzf-tCRf1eJt9kN0ZQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-21  0:12                           ` Martin K. Petersen [this message]
2015-06-22 14:32                           ` Alan Stern

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-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tom.ty89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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