public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zach Brown <zach.brown@oracle.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: akpm@osdl.org, andrea@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Shrink rbtree
Date: Fri, 21 Apr 2006 11:24:03 -0700	[thread overview]
Message-ID: <44492343.6040603@oracle.com> (raw)
In-Reply-To: <1145623663.11909.139.camel@pmac.infradead.org>


> the pointers are always going to be aligned. So let's just use the
> lowest bit of the parent pointer instead. This shrinks the rb_node from
> 4 machine-words to 3.

We've seen this patch before, haven't we? :)  I still like it.

> Another pair of eyes on the 'remove dead code in rb_erase()' bit in
> particular would be appreciated.

I'll trade you some eyes for a description beyond the four words
obvious, remove, dead, and code.

>  struct rb_node
>  {
> -	struct rb_node *rb_parent;
> -	int rb_color;
> +	unsigned long  rb_parent_colour;

How about some kerneldoc comments?

>  #define	RB_RED		0
>  #define	RB_BLACK	1

> +#define rb_colour(r)   ((r)->rb_parent_colour & 1)

This creates a pretty strong bond between the two.. maybe a
RB_COLOUR_MASK and use that and the _RED/_BLACK defines instead of the
raw constants?

> +#define rb_is_red(r)   (!rb_colour(r))
> +#define rb_is_black(r) rb_colour(r)
> +#define rb_set_red(r)  do { (r)->rb_parent_colour &= ~1; } while (0)
> +#define rb_set_black(r)  do { (r)->rb_parent_colour |= 1; } while (0)
> +
> +static inline void rb_set_parent(struct rb_node *rb, struct rb_node *p)
> +{

	BUG_ON((unsigned long)p & 3);

> +	rb->rb_parent_colour = (rb->rb_parent_colour & 3) | (unsigned long)p;
> +}
> +static inline void rb_set_colour(struct rb_node *rb, int colour)
> +{
> +	rb->rb_parent_colour = (rb->rb_parent_colour & ~1) | colour;
> +}
> +
>  #define RB_ROOT	(struct rb_root) { NULL, }
>  #define	rb_entry(ptr, type, member) container_of(ptr, type, member)
>  
> @@ -131,8 +147,7 @@ extern void rb_replace_node(struct rb_no
>  static inline void rb_link_node(struct rb_node * node, struct rb_node * parent,
>  				struct rb_node ** rb_link)
>  {
> -	node->rb_parent = parent;
> -	node->rb_color = RB_RED;
> +	node->rb_parent_colour = (unsigned long )parent;

use rb_set_parent(node, parent) and get the assertion.

- z

  parent reply	other threads:[~2006-04-21 18:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 12:47 [PATCH] Shrink rbtree David Woodhouse
2006-04-21 13:06 ` Nick Piggin
2006-04-21 19:08   ` David Woodhouse
2006-04-21 20:57     ` Hugh Dickins
2006-04-21 22:12       ` David Woodhouse
2006-04-23 13:03         ` Hugh Dickins
2006-04-21 18:24 ` Zach Brown [this message]
2006-04-21 19:06   ` David Woodhouse
2006-04-21 19:25     ` Zach Brown
2006-04-22  1:09 ` Andrew Morton
2006-04-22  1:10   ` Andrew Morton
2006-04-22  1:21     ` Andrew Morton
2006-04-22  1:29   ` David Woodhouse
2006-04-22 12:29     ` Ingo Oeser
2006-04-22 13:38       ` David Woodhouse
2006-04-22 22:55         ` Ingo Oeser
2006-04-23 16:36   ` Steven Rostedt
2006-04-23 17:20     ` Thomas Gleixner

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=44492343.6040603@oracle.com \
    --to=zach.brown@oracle.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.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