All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Kevin Bealer <kevinbealer@yahoo.com>
Cc: reiserfs-list@namesys.com, jmacd <jmacd@cs.berkeley.edu>
Subject: Re: binary treaps
Date: Thu, 08 May 2003 01:57:35 +0400	[thread overview]
Message-ID: <3EB9814F.6070405@namesys.com> (raw)
In-Reply-To: <20030507214245.73383.qmail@web40013.mail.yahoo.com>

Kevin Bealer wrote:

>On the namesys homepage, there is a statement that
>skip lists
>would be very good for directory contents but the node
>size
>varies.
>
>I wrote a balanced tree algorithm that works about
>like a skip
>list but does not have variable node size.  I started
>with the 'skip
>list' algorithm and developed a tree algorithm based
>on it.
>
>After developing this, I found an algorithm which is
>similar, called a 'treap', although they use an
>insert-then-rotate, and
>my version does the insert in one downward pass.
>
>I don't know enough about reiserfs's internals but I
>can send the
>tree algorithm description and code if anyone wants to
>see it.
>
>Kevin Bealer
>
>
>
>__________________________________
>Do you Yahoo!?
>The New Yahoo! Search - Faster. Easier. Bingo.
>http://search.yahoo.com
>
>
>  
>
Josh (jmacd) said that he did that also, but perhaps I did not listen 
carefully enough because I did not understand how it could be done.  If 
you randomly choose whether to insert into a given node or its children, 
how do you avoid randomly exceeding a fixed node size without 
balancing?   I must be misunderstanding one of the premises of the 
algorithm, or some such.

Yes, I would be interested in reading the algorithm description.

-- 
Hans



      reply	other threads:[~2003-05-07 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 21:42 binary treaps Kevin Bealer
2003-05-07 21:57 ` Hans Reiser [this message]

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=3EB9814F.6070405@namesys.com \
    --to=reiser@namesys.com \
    --cc=jmacd@cs.berkeley.edu \
    --cc=kevinbealer@yahoo.com \
    --cc=reiserfs-list@namesys.com \
    /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.