From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Werner Almesberger <werner@almesberger.net>
Cc: Rajesh Venkatasubramanian <vrajesh@umich.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Generalize prio_tree (1/3)
Date: Mon, 15 Nov 2004 15:30:53 +1100 [thread overview]
Message-ID: <419830FD.7000007@yahoo.com.au> (raw)
In-Reply-To: <20041114235646.K28802@almesberger.net>
Werner Almesberger wrote:
> Hi Rajesh,
>
> perhaps you remember me posting a long time ago about generalizing
> prio_tree. Now I finally got to make that patch. In fact, there are
> three parts:
>
> - the prio_tree "core" in lib/
> - switching mm/prio_tree.c to use the "core"
> - some debugging extensions
>
> The reason for wanting this generalization is that we'll also need
> radix priority search trees for healthier barrier handling in the
> IO scheduler (aka disk elevator).
>
I'm curious, how do you plan to use them for healthier barrier handling?
next prev parent reply other threads:[~2004-11-15 4:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 2:56 [RFC] Generalize prio_tree (1/3) Werner Almesberger
2004-11-15 2:59 ` [RFC] Make MM use generalized prio_tree (2/3) Werner Almesberger
2004-11-15 3:05 ` [RFC] prio_tree debugging functions (3/3) Werner Almesberger
2004-11-15 4:30 ` Nick Piggin [this message]
2004-11-15 6:07 ` [RFC] Generalize prio_tree (1/3) Werner Almesberger
2004-11-15 11:01 ` Nick Piggin
2004-11-15 14:32 ` Werner Almesberger
2004-11-15 18:13 ` Rajesh Venkatasubramanian
2004-11-15 20:54 ` Werner Almesberger
2004-11-15 21:14 ` Rajesh Venkatasubramanian
2004-11-15 21:42 ` Werner Almesberger
2004-11-15 22:27 ` Rajesh Venkatasubramanian
2004-11-15 22:59 ` Werner Almesberger
2004-11-16 0:07 ` Rajesh Venkatasubramanian
2004-11-16 0:35 ` Werner Almesberger
2004-11-16 1:48 ` Rajesh Venkatasubramanian
2004-11-16 23:51 ` Generalize prio_tree, 2nd try Werner Almesberger
2004-11-17 1:28 ` 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=419830FD.7000007@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=vrajesh@umich.edu \
--cc=werner@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.