From: Carl Henrik Lunde <chlunde@ping.uio.no>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: 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, matthew@wil.cx, 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 16:37:17 +0200 [thread overview]
Message-ID: <ed038eb20904240737u4d248b63s580f7d4d1831e173@mail.gmail.com> (raw)
In-Reply-To: <49F1B68D.3010304@garzik.org>
> 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.
[sorry for replying in the middle of the thread, but I didn't get the
original email]
--
mvh
Carl Henrik
next prev parent reply other threads:[~2009-04-24 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <patchbomb.1240551141@sermon.lab.mkp.net>
[not found] ` <72f4e15760670febdb40.1240551143@sermon.lab.mkp.net>
[not found] ` <ac3eb2510904240514y660973abj7621864e11e514f2@mail.gmail.com>
2009-04-24 12:54 ` Jeff Garzik
2009-04-24 14:37 ` Carl Henrik Lunde [this message]
2009-04-24 14:47 ` Matthew Wilcox
2009-04-24 15:16 ` Martin K. Petersen
2009-04-24 15:00 ` Martin K. Petersen
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=ed038eb20904240737u4d248b63s580f7d4d1831e173@mail.gmail.com \
--to=chlunde@ping.uio.no \
--cc=James.Bottomley@hansenpartnership.com \
--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=matthew@wil.cx \
--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
all inboxes | Powered by JetHome®