All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Michel Lespinasse <walken@google.com>
Cc: peterz@infradead.org, daniel.santos@pobox.com,
	aarcange@redhat.com, dwmw2@infradead.org,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] rbtree: optimize fetching of sibling node
Date: Tue, 24 Jul 2012 17:52:23 -0400	[thread overview]
Message-ID: <500F1917.2050308@redhat.com> (raw)
In-Reply-To: <1342787467-5493-3-git-send-email-walken@google.com>

On 07/20/2012 08:31 AM, Michel Lespinasse wrote:
> When looking to fetch a node's sibling, we went through a sequence of:
> - check if node is the parent's left child
> - if it is, then fetch the parent's right child
>
> This can be replaced with:
> - fetch the parent's right child as an assumed sibling
> - check that node is NOT the fetched child
>
> This avoids fetching the parent's left child when node is actually
> that child. Saves a bit on code size, though it doesn't seem to make
> a large difference in speed.
>
> Signed-off-by: Michel Lespinasse<walken@google.com>

Acked-by: Rik van Riel <riel@redhat.com>


-- 
All rights reversed

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Michel Lespinasse <walken@google.com>
Cc: peterz@infradead.org, daniel.santos@pobox.com,
	aarcange@redhat.com, dwmw2@infradead.org,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] rbtree: optimize fetching of sibling node
Date: Tue, 24 Jul 2012 17:52:23 -0400	[thread overview]
Message-ID: <500F1917.2050308@redhat.com> (raw)
In-Reply-To: <1342787467-5493-3-git-send-email-walken@google.com>

On 07/20/2012 08:31 AM, Michel Lespinasse wrote:
> When looking to fetch a node's sibling, we went through a sequence of:
> - check if node is the parent's left child
> - if it is, then fetch the parent's right child
>
> This can be replaced with:
> - fetch the parent's right child as an assumed sibling
> - check that node is NOT the fetched child
>
> This avoids fetching the parent's left child when node is actually
> that child. Saves a bit on code size, though it doesn't seem to make
> a large difference in speed.
>
> Signed-off-by: Michel Lespinasse<walken@google.com>

Acked-by: Rik van Riel <riel@redhat.com>


-- 
All rights reversed

  reply	other threads:[~2012-07-24 21:52 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 12:31 [RFC PATCH 0/6] augmented rbtree changes Michel Lespinasse
2012-07-20 12:31 ` Michel Lespinasse
2012-07-20 12:31 ` [PATCH 1/6] rbtree: rb_erase updates and comments Michel Lespinasse
2012-07-20 12:31   ` Michel Lespinasse
2012-07-24 18:50   ` Rik van Riel
2012-07-24 18:50     ` Rik van Riel
2012-07-20 12:31 ` [PATCH 2/6] rbtree: optimize fetching of sibling node Michel Lespinasse
2012-07-20 12:31   ` Michel Lespinasse
2012-07-24 21:52   ` Rik van Riel [this message]
2012-07-24 21:52     ` Rik van Riel
2012-07-20 12:31 ` [PATCH 3/6] augmented rbtree test Michel Lespinasse
2012-07-20 12:31   ` Michel Lespinasse
2012-07-25 15:42   ` Rik van Riel
2012-07-25 15:42     ` Rik van Riel
2012-07-20 12:31 ` [PATCH 4/6] rbtree: faster augmented insert Michel Lespinasse
2012-07-20 12:31   ` Michel Lespinasse
2012-07-25 16:10   ` Rik van Riel
2012-07-25 16:10     ` Rik van Riel
2012-07-25 17:54   ` Rik van Riel
2012-07-25 17:54     ` Rik van Riel
2012-07-27 19:26   ` Peter Zijlstra
2012-07-27 19:26     ` Peter Zijlstra
2012-07-27 21:43     ` Michel Lespinasse
2012-07-27 21:43       ` Michel Lespinasse
2012-07-27 19:31   ` Peter Zijlstra
2012-07-27 19:31     ` Peter Zijlstra
2012-07-27 20:04   ` Peter Zijlstra
2012-07-27 20:04     ` Peter Zijlstra
2012-07-27 21:55     ` Michel Lespinasse
2012-07-27 21:55       ` Michel Lespinasse
2012-07-20 12:31 ` [PATCH 5/6] rbtree: faster augmented erase Michel Lespinasse
2012-07-20 12:31   ` Michel Lespinasse
2012-07-24  1:54   ` Michel Lespinasse
2012-07-24  1:54     ` Michel Lespinasse
2012-07-25 17:53     ` Rik van Riel
2012-07-25 17:53       ` Rik van Riel
2012-07-27 19:43   ` Peter Zijlstra
2012-07-27 19:43     ` Peter Zijlstra
2012-07-27 20:02   ` Peter Zijlstra
2012-07-27 20:02     ` Peter Zijlstra
2012-07-28  0:44     ` Michel Lespinasse
2012-07-28  0:44       ` Michel Lespinasse
2012-07-28  2:31       ` Michel Lespinasse
2012-07-28  2:31         ` Michel Lespinasse
2012-07-20 12:31 ` [PATCH 6/6] rbtree: remove prior augmented rbtree implementation Michel Lespinasse
2012-07-20 12:31   ` Michel Lespinasse
2012-07-24  1:55   ` Michel Lespinasse
2012-07-24  1:55     ` Michel Lespinasse
2012-07-25 17:59     ` Rik van Riel
2012-07-25 17:59       ` Rik van Riel
2012-07-24  1:46 ` [RFC PATCH 0/6] augmented rbtree changes Michel Lespinasse
2012-07-24  1:46   ` Michel Lespinasse

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=500F1917.2050308@redhat.com \
    --to=riel@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.santos@pobox.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterz@infradead.org \
    --cc=walken@google.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.