From: Werner Almesberger <werner@almesberger.net>
To: linux-kernel@vger.kernel.org
Cc: Rajesh Venkatasubramanian <vrajesh@umich.edu>,
Andrew Morton <akpm@osdl.org>
Subject: [PATCH 0/3] prio_tree generalization
Date: Fri, 17 Dec 2004 15:36:02 -0300 [thread overview]
Message-ID: <20041217153602.D31842@almesberger.net> (raw)
This patch set for 2.6.10-rc3-bk10 (*) generalizes the prio_tree
code such that other subsystems than just VMA can use it.
(*) I'm not sure which tree is the most useful base for this.
Should I use 2.6.10-rc3-mm* instead of -bk* ? (Or is it
already too late for 2.6.10 anyway ?)
While there are currently no other in-tree users than VMA,
the prio_tree algorithm will be useful for detecting overlapping
disk IO requests, which is a prerequisite for efficient handling
of barriers, which - besides being a good idea in general - in
turn is a prerequisite for useful disk IO priorities.
The three patches that follow are incremental and must be applied
in the order specified.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next reply other threads:[~2004-12-17 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 18:36 Werner Almesberger [this message]
2004-12-17 18:37 ` [PATCH 1/3] prio_tree: roll call to prio_tree_first into prio_tree_next Werner Almesberger
2004-12-17 18:39 ` [PATCH 2/3] prio_tree: generalization Werner Almesberger
2004-12-17 18:40 ` [PATCH 3/3] prio_tree: move general code from mm/ to lib/ Werner Almesberger
2004-12-17 19:52 ` [PATCH 0/3] prio_tree generalization Andrew Morton
2004-12-17 23:10 ` [PATCH 3/3] prio_tree: move general code from mm/ to lib/ David Howells
2004-12-17 23:16 ` 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=20041217153602.D31842@almesberger.net \
--to=werner@almesberger.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vrajesh@umich.edu \
/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.