From: Michel Lespinasse <walken@google.com> To: aarcange@redhat.com, dwmw2@infradead.org, riel@redhat.com, peterz@infradead.org, daniel.santos@pobox.com, axboe@kernel.dk, ebiederm@xmission.com Cc: linux-mm@kvack.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org Subject: [PATCH 06/13] rbtree: break out of rb_insert_color loop after tree rotation Date: Mon, 9 Jul 2012 16:35:16 -0700 [thread overview] Message-ID: <1341876923-12469-7-git-send-email-walken@google.com> (raw) In-Reply-To: <1341876923-12469-1-git-send-email-walken@google.com> It is a well known property of rbtrees that insertion never requires more than two tree rotations. In our implementation, after one loop iteration identified one or two necessary tree rotations, we would iterate and look for more. However at that point the node's parent would always be black, which would cause us to exit the loop. We can make the code flow more obvious by just adding a break statement after the tree rotations, where we know we are done. Additionally, in the cases where two tree rotations are necessary, we don't have to update the 'node' pointer as it wouldn't be used until the next loop iteration, which we now avoid due to this break statement. Signed-off-by: Michel Lespinasse <walken@google.com> --- lib/rbtree.c | 14 ++++---------- 1 files changed, 4 insertions(+), 10 deletions(-) diff --git a/lib/rbtree.c b/lib/rbtree.c index d0ec339..19bee6c 100644 --- a/lib/rbtree.c +++ b/lib/rbtree.c @@ -109,18 +109,15 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root) } } - if (parent->rb_right == node) - { - register struct rb_node *tmp; + if (parent->rb_right == node) { __rb_rotate_left(parent, root); - tmp = parent; parent = node; - node = tmp; } rb_set_black(parent); rb_set_red(gparent); __rb_rotate_right(gparent, root); + break; } else { { register struct rb_node *uncle = gparent->rb_left; @@ -134,18 +131,15 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root) } } - if (parent->rb_left == node) - { - register struct rb_node *tmp; + if (parent->rb_left == node) { __rb_rotate_right(parent, root); - tmp = parent; parent = node; - node = tmp; } rb_set_black(parent); rb_set_red(gparent); __rb_rotate_left(gparent, root); + break; } } -- 1.7.7.3
WARNING: multiple messages have this Message-ID (diff)
From: Michel Lespinasse <walken@google.com> To: aarcange@redhat.com, dwmw2@infradead.org, riel@redhat.com, peterz@infradead.org, daniel.santos@pobox.com, axboe@kernel.dk, ebiederm@xmission.com Cc: linux-mm@kvack.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org Subject: [PATCH 06/13] rbtree: break out of rb_insert_color loop after tree rotation Date: Mon, 9 Jul 2012 16:35:16 -0700 [thread overview] Message-ID: <1341876923-12469-7-git-send-email-walken@google.com> (raw) In-Reply-To: <1341876923-12469-1-git-send-email-walken@google.com> It is a well known property of rbtrees that insertion never requires more than two tree rotations. In our implementation, after one loop iteration identified one or two necessary tree rotations, we would iterate and look for more. However at that point the node's parent would always be black, which would cause us to exit the loop. We can make the code flow more obvious by just adding a break statement after the tree rotations, where we know we are done. Additionally, in the cases where two tree rotations are necessary, we don't have to update the 'node' pointer as it wouldn't be used until the next loop iteration, which we now avoid due to this break statement. Signed-off-by: Michel Lespinasse <walken@google.com> --- lib/rbtree.c | 14 ++++---------- 1 files changed, 4 insertions(+), 10 deletions(-) diff --git a/lib/rbtree.c b/lib/rbtree.c index d0ec339..19bee6c 100644 --- a/lib/rbtree.c +++ b/lib/rbtree.c @@ -109,18 +109,15 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root) } } - if (parent->rb_right == node) - { - register struct rb_node *tmp; + if (parent->rb_right == node) { __rb_rotate_left(parent, root); - tmp = parent; parent = node; - node = tmp; } rb_set_black(parent); rb_set_red(gparent); __rb_rotate_right(gparent, root); + break; } else { { register struct rb_node *uncle = gparent->rb_left; @@ -134,18 +131,15 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root) } } - if (parent->rb_left == node) - { - register struct rb_node *tmp; + if (parent->rb_left == node) { __rb_rotate_right(parent, root); - tmp = parent; parent = node; - node = tmp; } rb_set_black(parent); rb_set_red(gparent); __rb_rotate_left(gparent, root); + break; } } -- 1.7.7.3 -- 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>
next prev parent reply other threads:[~2012-07-09 23:35 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-09 23:35 [PATCH 00/13] rbtree updates Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 01/13] rbtree: reference Documentation/rbtree.txt for usage instructions Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-10 1:45 ` Rik van Riel 2012-07-10 1:45 ` Rik van Riel 2012-07-09 23:35 ` [PATCH 02/13] rbtree: empty nodes have no color Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-10 10:59 ` Daniel Santos 2012-07-10 10:59 ` Daniel Santos 2012-07-10 23:10 ` Michel Lespinasse 2012-07-10 23:10 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 03/13] rbtree: fix incorrect rbtree node insertion in fs/proc/proc_sysctl.c Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 04/13] rbtree: move some implementation details from rbtree.h to rbtree.c Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-10 12:19 ` Michal Nazarewicz 2012-07-10 12:19 ` Michal Nazarewicz 2012-07-10 23:12 ` Michel Lespinasse 2012-07-10 23:12 ` Michel Lespinasse 2012-07-11 15:48 ` Michal Nazarewicz 2012-07-11 15:48 ` Michal Nazarewicz 2012-07-09 23:35 ` [PATCH 05/13] rbtree: performance and correctness test Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-10 12:27 ` Michal Nazarewicz 2012-07-10 12:27 ` Michal Nazarewicz 2012-07-10 23:18 ` Michel Lespinasse 2012-07-10 23:18 ` Michel Lespinasse 2012-07-11 6:14 ` Michel Lespinasse 2012-07-11 6:14 ` Michel Lespinasse 2012-07-11 19:30 ` Daniel Santos 2012-07-11 19:30 ` Daniel Santos 2012-07-09 23:35 ` Michel Lespinasse [this message] 2012-07-09 23:35 ` [PATCH 06/13] rbtree: break out of rb_insert_color loop after tree rotation Michel Lespinasse 2012-07-09 23:35 ` [PATCH 07/13] rbtree: adjust root color in rb_insert_color() only when necessary Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 08/13] rbtree: optimize tree rotations in rb_insert_color() Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 09/13] rbtree: optimize color flips and parent fetching " Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 10/13] rbtree: adjust node color in __rb_erase_color() only when necessary Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 11/13] rbtree: optimize case selection logic in __rb_erase_color() Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 12/13] rbtree: optimize tree rotations " Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-09 23:35 ` [PATCH 13/13] rbtree: optimize color flips " Michel Lespinasse 2012-07-09 23:35 ` Michel Lespinasse 2012-07-11 13:23 ` [PATCH 00/13] rbtree updates Peter Zijlstra 2012-07-11 13:23 ` Peter Zijlstra 2012-07-12 1:12 ` Michel Lespinasse 2012-07-12 1:12 ` Michel Lespinasse 2012-07-12 14:09 ` Peter Zijlstra 2012-07-12 14:09 ` Peter Zijlstra 2012-07-12 14:12 ` Peter Zijlstra 2012-07-12 14:12 ` Peter Zijlstra 2012-07-13 0:39 ` Michel Lespinasse 2012-07-13 0:39 ` 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=1341876923-12469-7-git-send-email-walken@google.com \ --to=walken@google.com \ --cc=aarcange@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=axboe@kernel.dk \ --cc=daniel.santos@pobox.com \ --cc=dwmw2@infradead.org \ --cc=ebiederm@xmission.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=peterz@infradead.org \ --cc=riel@redhat.com \ --cc=torvalds@linux-foundation.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: linkBe 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.