From: Nick Piggin <piggin@cyberone.com.au>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Benefits from computing physical IDE disk geometry?
Date: Mon, 14 Apr 2003 13:58:55 +1000 [thread overview]
Message-ID: <3E9A31FF.6030506@cyberone.com.au> (raw)
In-Reply-To: <1050272156.24559.4.camel@dhcp22.swansea.linux.org.uk>
Alan Cox wrote:
>On Sul, 2003-04-13 at 19:03, Chuck Ebbert wrote:
>
>> OTOH you can come up with scenarios like, say, a DBMS doing 16K page
>>aligned IO to raw devices where you might see big gains from making sure
>>those 16K chunks didn't cross a physical cylinder boundary.
>>
>
>You couldn't even tell where such boundaries exist, or what the real
>block size of the underlying media is. Cyliners are all different sizes.
>
Yes this is getting very difficult as Alan said. Its also something
that we can't do in kernel - the block io scheduler can only choose
from what it is given. I wouldn't be surprised if big databases did
try using some sorts of disk mapping systems to help optimise
their IO however.
next prev parent reply other threads:[~2003-04-14 4:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 18:03 Benefits from computing physical IDE disk geometry? Chuck Ebbert
2003-04-13 18:24 ` Dr. David Alan Gilbert
2003-04-13 18:32 ` Lars Marowsky-Bree
2003-04-13 18:51 ` Dr. David Alan Gilbert
2003-04-13 22:14 ` Alan Cox
2003-04-14 0:17 ` Andreas Dilger
2003-04-13 22:15 ` Alan Cox
2003-04-14 3:58 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 13:28 Chuck Ebbert
2003-04-16 23:06 ` Nick Piggin
2003-04-15 18:33 Chuck Ebbert
2003-04-16 1:16 ` Nick Piggin
2003-04-16 1:59 ` Nick Piggin
2003-04-15 1:19 Chuck Ebbert
2003-04-15 8:28 ` Nick Piggin
2003-04-14 21:27 Chuck Ebbert
2003-04-15 0:03 ` Nick Piggin
2003-04-14 3:44 Chuck Ebbert
2003-04-14 2:29 Chuck Ebbert
2003-04-13 22:13 Chuck Ebbert
2003-04-13 23:38 ` Andreas Dilger
2003-04-12 22:46 Timothy Miller
2003-04-13 9:51 ` John Bradford
2003-04-13 11:50 ` Nick Piggin
2003-04-13 15:25 ` Timothy Miller
2003-04-14 3:52 ` Nick Piggin
2003-04-14 6:44 ` Mark Hahn
2003-04-14 13:28 ` Nick Piggin
2003-04-13 14:29 ` Alan Cox
2003-04-13 16:15 ` John Bradford
2003-04-18 13:01 ` Helge Hafting
2003-04-18 13:25 ` John Bradford
2003-04-14 18:27 ` Wes Felter
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=3E9A31FF.6030506@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=76306.1226@compuserve.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.