From: Andrew Morton <akpm@digeo.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Frederic Rossi (LMC)" <Frederic.Rossi@ericsson.ca>, linux-mm@kvack.org
Subject: Re: freemaps
Date: Sun, 15 Dec 2002 01:03:26 -0800 [thread overview]
Message-ID: <3DFC455E.1FD92CBC@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212150926130.1831-100000@localhost.localdomain>
Ingo Molnar wrote:
>
> ...
> another approach might be to maintain some sort of tree of holes.
This one, I'd suggest. If we're going to fix this we may as
well fix it right. Otherwise there will always be whacky failure
modes.
Trees are tricky, because we don't like to recur.
I expect this could be solved with two trees:
- For searching, a radix-tree indexed by hole size. A list
of same-sized holes at each leaf.
- For insertion (where we must perform merging) an rbtree.
But:
- Do we need to keep the lists of same-sized holes sorted by
virtual address, to avoid fragmentation?
- Do all mm's incur all this stuff, or do we build it all when
some threshold is crossed?
- How does it play with non-linear mappings?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-12-15 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 22:47 freemaps Frederic Rossi (LMC)
2002-12-15 3:09 ` freemaps Andrew Morton
2002-12-15 8:41 ` freemaps Ingo Molnar
2002-12-15 9:03 ` Andrew Morton [this message]
2002-12-15 9:36 ` freemaps Ingo Molnar
2002-12-16 0:51 ` freemaps William Lee Irwin III
2002-12-16 1:03 ` freemaps Andrew Morton
2002-12-16 1:09 ` freemaps William Lee Irwin III
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=3DFC455E.1FD92CBC@digeo.com \
--to=akpm@digeo.com \
--cc=Frederic.Rossi@ericsson.ca \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
/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