From: Bill Davidsen <davidsen@tmr.com>
To: Vishal Patil <vishpat@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CSCAN I/O scheduler for 2.6.10 kernel
Date: Tue, 04 Apr 2006 16:28:04 -0400 [thread overview]
Message-ID: <4432D6D4.2020102@tmr.com> (raw)
In-Reply-To: <4745278c0603301958o4c2ed282x3513fdb459d8ec7c@mail.gmail.com>
Vishal Patil wrote:
> Maintain two queues which will be sorted in ascending order using Red
> Black Trees. When a disk request arrives and if the block number it
> refers to is greater than the block number of the current request
> being served add (merge) it to the first sorted queue or else add
> (merge) it to the second sorted queue. Keep on servicing the requests
> from the first request queue until it is empty after which switch over
> to the second queue and now reverse the roles of the two queues.
> Simple and Sweet. Many thanks for the awesome block I/O layer in the
> 2.6 kernel.
>
Why both queues sorting in ascending order? I would think that one
should be in descending order, which would reduce the seek distance
between the last i/o on one queue and the first on the next.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2006-04-04 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4745278c0603301955w26fea42eid6bcab91c573eaa3@mail.gmail.com>
2006-03-31 3:58 ` CSCAN I/O scheduler for 2.6.10 kernel Vishal Patil
2006-03-31 6:28 ` Matt Heler
2006-03-31 14:16 ` Vishal Patil
2006-04-04 20:28 ` Bill Davidsen [this message]
2006-04-04 21:02 ` Vishal Patil
2006-04-05 11:48 ` Antonio Vargas
2006-04-05 13:46 ` Vishal Patil
2006-04-09 16:55 ` Vishal Patil
2006-04-11 11:34 ` Jan Engelhardt
2006-04-11 11:39 ` Jens Axboe
2006-04-11 11:42 ` Jan Engelhardt
2006-04-11 11:43 ` Jens Axboe
2006-04-12 23:53 ` Vishal Patil
2006-04-13 14:04 ` Jan Engelhardt
2006-04-05 9:20 ` Jens Axboe
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=4432D6D4.2020102@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vishpat@gmail.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