From: Andrew Morton <akpm@osdl.org>
To: Werner Almesberger <wa@almesberger.net>
Cc: vrajesh@umich.edu, linux-kernel@vger.kernel.org
Subject: Re: prio_tree generalization
Date: Sun, 4 Jul 2004 21:46:09 -0700 [thread overview]
Message-ID: <20040704214609.71b0084d.akpm@osdl.org> (raw)
In-Reply-To: <20040704222438.A11865@almesberger.net>
Werner Almesberger <wa@almesberger.net> wrote:
>
> I'm currently experimenting with the prio_tree code in an elevator
> ("IO scheduler"),
Offtopic, but that's a premature optmztn. O(n) linear searches work just
fine for disk elevators under most circumstances - we don't get may
complaints about CPU consumption in the 2.4 elevator.
A disk isn't going to retire more than 100 requests/sec in practice, and
the cost of an all-requests search is relatively small.
Once the new design is settled in, is proven to be useful and desirable,
that's the time to start thinking about millioptimisations such as
converting the search complexity from O(n) to O(log(n)).
next prev parent reply other threads:[~2004-07-05 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 1:24 prio_tree generalization Werner Almesberger
2004-07-05 2:07 ` Andrea Arcangeli
2004-07-05 2:36 ` Werner Almesberger
2004-07-05 4:46 ` Andrew Morton [this message]
2004-07-05 11:05 ` Werner Almesberger
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=20040704214609.71b0084d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vrajesh@umich.edu \
--cc=wa@almesberger.net \
/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.