linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@zip.com.au>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] generic nonlinear mappings, 2.5.44-mm2-D0
Date: Wed, 23 Oct 2002 16:23:42 +0200	[thread overview]
Message-ID: <20021023142342.GC1912@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0210231618150.10431-100000@localhost.localdomain>

On Wed, Oct 23, 2002 at 04:20:30PM +0200, Ingo Molnar wrote:
> 
> On Wed, 23 Oct 2002, Andrea Arcangeli wrote:
> 
> > it's not another vma tree, furthmore another vma tree indexed by the
> > hole size wouldn't be able to defragment and it would find the best fit
> > not the first fit on the left.
> 
> what i was talking about was a hole-tree indexed by the hole start

yes an hole tree.

> address, not a vma tree indexed by the hole size. (the later is pretty

indexed by the hole start address? then it's still O(N), then your quick
cache for the first hole would not be much different. I above meant hole
size, then it would be O(log(N)), but it wouldn't defragment anymore.

> pointless.) And even this solution still has to search the tree linearly
> for a matching hole.

exactly, it's still O(N).

The final solution needed isn't a plain tree, it needs modifications to
the rbtree code to make the data structure more powerful, that will
provide that info in O(log(N)) without an additional tree and starting
from the left (i.e. it won't alter the retval of get_unmapped_area, just
its speed).  the design is just finished for some time, what's left is
to implement it and it isn't trivial ;).

Anyways this O(log(N)) complexity improvement is needed anyways, old
applications will be still around in particular when they will find they
don't need special API to work fast.

Andrea
--
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/

  reply	other threads:[~2002-10-23 14:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 17:57 Ingo Molnar
2002-10-22 17:49 ` Christoph Hellwig
2002-10-22 19:23   ` Andrew Morton
2002-10-22 20:27     ` Ingo Molnar
2002-10-22 20:38       ` Alan Cox
2002-10-22 20:42         ` Ingo Molnar
2002-10-22 21:18           ` Alan Cox
2002-10-23 19:09           ` Bryan O'Sullivan
2002-10-22 20:49         ` Ingo Molnar
2002-10-22 20:19   ` Ingo Molnar
2002-10-23  2:05     ` Andrea Arcangeli
2002-10-23  7:19       ` Ingo Molnar
2002-10-23 11:50         ` Andrea Arcangeli
2002-10-23 14:20           ` Ingo Molnar
2002-10-23 14:23             ` Andrea Arcangeli [this message]
2002-10-22 19:13 ` Rik van Riel
2002-10-22 22:27 ` David S. Miller
2002-10-22 22:56   ` Ingo Molnar

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=20021023142342.GC1912@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@zip.com.au \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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