All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <werner@almesberger.net>
To: Rajesh Venkatasubramanian <vrajesh@umich.edu>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Generalize prio_tree (1/3)
Date: Mon, 15 Nov 2004 21:35:15 -0300	[thread overview]
Message-ID: <20041115213515.B28802@almesberger.net> (raw)
In-Reply-To: <Pine.GSO.4.58.0411151814440.6691@lazuli.engin.umich.edu>; from vrajesh@umich.edu on Mon, Nov 15, 2004 at 07:07:39PM -0500

Rajesh Venkatasubramanian wrote:
> Yeap. That looks sane. However, if you are planning to produce
> a patch, please consider the following names:
> 
> 	struct prio_tree_node {
> 		unsigned long start, end;
> 		struct raw_prio_tree_node prio_tree_node;
> 	};

Okay. Any reason why you've put "start, end" before "prio_tree_node" ?
The other way around would seem to make things a lot easier.

> I think the r_index and h_index names are only meaningful in
> prio_tree.c. My guess is start and end will be more palatable
> to users of prio_tree.

Yes, they're a bit confusing :-) It would actually be nice if you
could write a little paper describing this particular type of radix
priority search tree, since it differs quite a bit from the original.
Also, the original paper is comparably difficult to obtain if you
don't have a university library at hand. Better documentation of how
prio_tree works might also encourage new uses of it.

Thanks,
- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina     werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  reply	other threads:[~2004-11-16  0:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15  2:56 [RFC] Generalize prio_tree (1/3) Werner Almesberger
2004-11-15  2:59 ` [RFC] Make MM use generalized prio_tree (2/3) Werner Almesberger
2004-11-15  3:05   ` [RFC] prio_tree debugging functions (3/3) Werner Almesberger
2004-11-15  4:30 ` [RFC] Generalize prio_tree (1/3) Nick Piggin
2004-11-15  6:07   ` Werner Almesberger
2004-11-15 11:01     ` Nick Piggin
2004-11-15 14:32       ` Werner Almesberger
2004-11-15 18:13 ` Rajesh Venkatasubramanian
2004-11-15 20:54   ` Werner Almesberger
2004-11-15 21:14     ` Rajesh Venkatasubramanian
2004-11-15 21:42       ` Werner Almesberger
2004-11-15 22:27         ` Rajesh Venkatasubramanian
2004-11-15 22:59           ` Werner Almesberger
2004-11-16  0:07             ` Rajesh Venkatasubramanian
2004-11-16  0:35               ` Werner Almesberger [this message]
2004-11-16  1:48                 ` Rajesh Venkatasubramanian
2004-11-16 23:51               ` Generalize prio_tree, 2nd try Werner Almesberger
2004-11-17  1:28                 ` 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=20041115213515.B28802@almesberger.net \
    --to=werner@almesberger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --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.