From: Matthew Wilcox <matthew@wil.cx>
To: Carl Henrik Lunde <chlunde@ping.uio.no>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Jeff Garzik <jeff@garzik.org>, Kay Sievers <kay.sievers@vrfy.org>,
rwheeler@redhat.com, snitzer@redhat.com, neilb@suse.de,
James.Bottomley@hansenpartnership.com, dgilbert@interlog.com,
jens.axboe@oracle.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2 of 9] block: Export I/O topology for block devices and partitions
Date: Fri, 24 Apr 2009 08:47:06 -0600 [thread overview]
Message-ID: <20090424144706.GC1926@parisc-linux.org> (raw)
In-Reply-To: <ed038eb20904240737u4d248b63s580f7d4d1831e173@mail.gmail.com>
On Fri, Apr 24, 2009 at 04:37:17PM +0200, Carl Henrik Lunde wrote:
> > On Fri, Apr 24, 2009 at 07:32, Martin K. Petersen <martin.petersen@oracle.com> wrote:
> > +What: ? ? ? ? ?/sys/block/<disk>/alignment
> > +What: ? ? ? ? ?/sys/block/<disk>/<partition>/alignment
> > +What: ? ? ? ? ?/sys/block/<disk>/queue/minimum_io_size
> > +What: ? ? ? ? ?/sys/block/<disk>/queue/optimal_io_size
>
> Would it also be possible and useful to include the number of
> spindles/channels, i.e., how many requests the device can handle
> concurrently? CFQ could for example serve two time slices
> concurrently if you have sequential reads and the device reports two
> spindles.
This is what we call "creeping featurism" (or other names not as nice).
You'll then want to know which data are provided by which spindle.
Then you'll want to know how fast each spindle is. Then you'll find that
not all storage gives you that information (try asking an EMC Symmetrix
how many spindles it has and where data is mapped ...)
Let's just get something merged which gives us an improvement.
Then you're free to experiment with adding the spindles count yourself,
and if you can show a real advantage to it, come back and we can argue
over it with data.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-04-24 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 5:32 [PATCH 0 of 9] I/O topology patch kit Martin K. Petersen
2009-04-24 5:32 ` [PATCH 1 of 9] block: Expose stacked device queues in sysfs Martin K. Petersen
2009-04-24 5:32 ` [PATCH 2 of 9] block: Export I/O topology for block devices and partitions Martin K. Petersen
2009-04-24 12:14 ` Kay Sievers
2009-04-24 12:54 ` Jeff Garzik
2009-04-24 14:37 ` Carl Henrik Lunde
2009-04-24 14:47 ` Matthew Wilcox [this message]
2009-04-24 15:16 ` Martin K. Petersen
2009-04-24 15:00 ` Martin K. Petersen
2009-04-24 14:53 ` Martin K. Petersen
2009-04-24 5:32 ` [PATCH 3 of 9] MD: Use new topology calls to indicate alignment and I/O sizes Martin K. Petersen
2009-04-24 5:32 ` [PATCH 4 of 9] sd: Physical block size and alignment support Martin K. Petersen
2009-04-24 5:32 ` [PATCH 5 of 9] sd: Detect non-rotational devices Martin K. Petersen
2009-04-24 5:32 ` [PATCH 6 of 9] sd: Block limits VPD support Martin K. Petersen
2009-04-24 5:32 ` [PATCH 7 of 9] scsi_debug: Add support for physical block exponent and alignment Martin K. Petersen
2009-04-24 5:32 ` [PATCH 8 of 9] libata: Report disk alignment and physical block size Martin K. Petersen
2009-04-24 5:32 ` [PATCH 9 of 9] libata: Media rotation rate and form factor heuristics Martin K. Petersen
[not found] ` <7ec2d82b188a9e9d4c56.1240551148@sermon.lab.mkp.net>
2009-04-24 6:10 ` [PATCH 7 of 9] scsi_debug: Add support for physical block exponent and alignment Douglas Gilbert
2009-04-24 6:14 ` Martin K. Petersen
[not found] ` <2fc5b2aa370a8ad47db1.1240551150@sermon.lab.mkp.net>
2009-04-24 12:30 ` [PATCH 9 of 9] libata: Media rotation rate and form factor heuristics Matthew Wilcox
[not found] ` <47f4f448a804a2d24f10.1240551149@sermon.lab.mkp.net>
2009-04-24 12:32 ` [PATCH 8 of 9] libata: Report disk alignment and physical block size Matthew Wilcox
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=20090424144706.GC1926@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@hansenpartnership.com \
--cc=chlunde@ping.uio.no \
--cc=dgilbert@interlog.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neilb@suse.de \
--cc=rwheeler@redhat.com \
--cc=snitzer@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).