From: Nick Piggin <piggin@cyberone.com.au>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Benefits from computing physical IDE disk geometry?
Date: Tue, 15 Apr 2003 10:03:55 +1000 [thread overview]
Message-ID: <3E9B4C6B.5020905@cyberone.com.au> (raw)
In-Reply-To: <200304141731_MC3-1-3462-2342@compuserve.com>
Chuck Ebbert wrote:
>Nick Piggin wrote:
>
>
>>There is (in AS) no cost function further than comparing distance
>>from the head. Closest forward seek wins.
>>
>
>
> The RAID1 code has its own scheduler that does similar things. Why
>aren't they being integrated? (See raid1.c:read_balance())
>
If RAID1 can use the generic elevator then it should. I
guess it can't though.
next prev parent reply other threads:[~2003-04-14 23:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 21:27 Benefits from computing physical IDE disk geometry? Chuck Ebbert
2003-04-15 0:03 ` 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 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-13 18:03 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
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=3E9B4C6B.5020905@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=76306.1226@compuserve.com \
--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.