linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin O'Connor" <koconnor@cse.Buffalo.EDU>
To: linux-mm@kvack.org
Subject: [PATCH] Generic AVL-Trees in MM code
Date: Mon, 17 Jan 2000 01:33:35 -0500	[thread overview]
Message-ID: <20000117013335.B12867@armstrong.cse.Buffalo.EDU> (raw)

[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]


Hello,

I recently sent a patch to the vger's mailing list with a new AVL Tree
implementation.  The idea is to reuse the same AVL code in multiple
places.  Since the MM code is one of the biggest changes in the patch I
thought I'd send an additional email to this group.  Any comments on the
patch?

-Kevin

Original linux-kernel email:

As of kernel 2.3.37 there are three separate AVL Tree implementations.
Included is a patch which implements generic AVL-Trees (ala linux/list.h)
and converts the existing code to use the new mechanisms.
     
The existing uses of AVL Trees are in:
linux/mm/mmap_tree.c
linux/net/bridge/br_tree.c
linux/net/ipv4/inetpeer.c 

The attached patch is in gzip form, alternatively it may be obtained from:
http://www.cse.buffalo.edu/~koconnor/kernel-avl-patch-1.1c

The patch is against 2.3.39, but since these files rarely change, it will
probably also apply to previous and/or later versions.

Comments? 
-Kevin

-- 
 ------------------------------------------------------------------------
 | Kevin O'Connor                     "BTW, IMHO we need a FAQ for      |
 | koconnor@cse.buffalo.edu            'IMHO', 'FAQ', 'BTW', etc. !"    |
 ------------------------------------------------------------------------

[-- Attachment #2: kernel-avl-patch-1.1c.gz --]
[-- Type: application/x-gzip, Size: 16311 bytes --]

                 reply	other threads:[~2000-01-17  6:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20000117013335.B12867@armstrong.cse.Buffalo.EDU \
    --to=koconnor@cse.buffalo.edu \
    --cc=linux-mm@kvack.org \
    /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