xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Praveen Kumar <kpraveen.lkml@gmail.com>
To: xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	konrad.wilk@oracle.com, George.Dunlap@eu.citrix.com,
	andrew.cooper3@citrix.com, dario.faggioli@citrix.com,
	ian.jackson@eu.citrix.com, tim@xen.org, kpraveen.lkml@gmail.com,
	jbeulich@suse.com
Subject: [PATCH v6 11/16 RESEND] rbtree: optimize fetching of sibling node
Date: Tue, 21 Nov 2017 20:50:04 +0530	[thread overview]
Message-ID: <20171121152009.15591-12-kpraveen.lkml@gmail.com> (raw)
In-Reply-To: <20171121152009.15591-1-kpraveen.lkml@gmail.com>

From: Michel Lespinasse <walken@google.com>

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>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: David Woodhouse <David.Woodhouse@intel.com>
Acked-by: Rik van Riel <riel@redhat.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Daniel Santos <daniel.santos@pobox.com>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[Linux commit 59633abf34e2f44b8e772a2c12a92132aa7c2220]

Ported to Xen.

Signed-off-by: Praveen Kumar <kpraveen.lkml@gmail.com>
---
 xen/common/rbtree.c | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/xen/common/rbtree.c b/xen/common/rbtree.c
index b964171bee..07b0875227 100644
--- a/xen/common/rbtree.c
+++ b/xen/common/rbtree.c
@@ -107,8 +107,8 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 
 		gparent = rb_red_parent(parent);
 
-		if (parent == gparent->rb_left) {
-			tmp = gparent->rb_right;
+		tmp = gparent->rb_right;
+		if (parent != tmp) {    /* parent == gparent->rb_left */
 			if (tmp && rb_is_red(tmp)) {
 				/*
 				 * Case 1 - color flips
@@ -131,7 +131,8 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 				continue;
 			}
 
-			if (parent->rb_right == node) {
+			tmp = parent->rb_right;
+			if (node == tmp) {
 				/*
 				 * Case 2 - left rotate at parent
 				 *
@@ -151,6 +152,7 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 							    RB_BLACK);
 				rb_set_parent_color(parent, node, RB_RED);
 				parent = node;
+				tmp = node->rb_right;
 			}
 
 			/*
@@ -162,7 +164,7 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 			 *     /                 \
 			 *    n                   U
 			 */
-			gparent->rb_left = tmp = parent->rb_right;
+			gparent->rb_left = tmp;  /* == parent->rb_right */
 			parent->rb_right = gparent;
 			if (tmp)
 				rb_set_parent_color(tmp, gparent, RB_BLACK);
@@ -180,7 +182,8 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 				continue;
 			}
 
-			if (parent->rb_left == node) {
+			tmp = parent->rb_left;
+			if (node == tmp) {
 				/* Case 2 - right rotate at parent */
 				parent->rb_left = tmp = node->rb_right;
 				node->rb_right = parent;
@@ -189,10 +192,11 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 							    RB_BLACK);
 				rb_set_parent_color(parent, node, RB_RED);
 				parent = node;
+				tmp = node->rb_left;
 			}
 
 			/* Case 3 - left rotate at gparent */
-			gparent->rb_right = tmp = parent->rb_left;
+			gparent->rb_right = tmp;  /* == parent->rb_left */
 			parent->rb_left = gparent;
 			if (tmp)
 				rb_set_parent_color(tmp, gparent, RB_BLACK);
@@ -223,8 +227,9 @@ static void __rb_erase_color(struct rb_node *node, struct rb_node *parent,
 			break;
 		} else if (!parent) {
 			break;
-		} else if (parent->rb_left == node) {
-			sibling = parent->rb_right;
+		}
+		sibling = parent->rb_right;
+		if (node != sibling) {  /* node == parent->rb_left */
 			if (rb_is_red(sibling)) {
 				/*
 				 * Case 1 - left rotate at parent
-- 
2.13.1


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-11-21 15:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 15:19 [PATCH v6 00/16] xen: common: rbtree: ported updates from Linux tree Praveen Kumar
2017-11-21 15:19 ` [PATCH v6 01/16] rbtree: remove redundant if()-condition in rb_erase() Praveen Kumar
2017-12-20 16:39   ` Jan Beulich
2017-11-21 15:19 ` [PATCH v6 02/16 RESEND] rbtree: empty nodes have no color Praveen Kumar
2017-12-20 16:43   ` Jan Beulich
2017-11-21 15:19 ` [PATCH v6 03/16 RESEND] rbtree: move some implementation details from rbtree.h to rbtree.c Praveen Kumar
2017-12-20 16:46   ` Jan Beulich
2017-11-21 15:19 ` [PATCH v6 04/16 RESEND] rbtree: break out of rb_insert_color loop after tree rotation Praveen Kumar
2017-12-20 16:49   ` Jan Beulich
2017-11-21 15:19 ` [PATCH v6 05/16 RESEND] rbtree: adjust root color in rb_insert_color() only when necessary Praveen Kumar
2017-12-20 16:51   ` Jan Beulich
2017-11-21 15:19 ` [PATCH v6 06/16 RESEND] rbtree: low level optimizations in rb_insert_color() Praveen Kumar
2017-12-20 16:52   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 07/16 RESEND] rbtree: adjust node color in __rb_erase_color() only when necessary Praveen Kumar
2017-12-20 16:55   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 08/16 RESEND] rbtree: optimize case selection logic in __rb_erase_color() Praveen Kumar
2017-12-20 16:57   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 09/16 RESEND] rbtree: low level optimizations " Praveen Kumar
2017-12-20 16:59   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 10/16 RESEND] rbtree: coding style adjustments Praveen Kumar
2018-01-03 11:26   ` Jan Beulich
2017-11-21 15:20 ` Praveen Kumar [this message]
2018-01-03 11:29   ` [PATCH v6 11/16 RESEND] rbtree: optimize fetching of sibling node Jan Beulich
2017-11-21 15:20 ` [PATCH v6 12/16 RESEND] rbtree: add __rb_change_child() helper function Praveen Kumar
2018-01-03 11:30   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 13/16 RESEND] rbtree: place easiest case first in rb_erase() Praveen Kumar
2018-01-03 11:32   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 14/16] rbtree: handle 1-child recoloring in rb_erase() instead of rb_erase_color() Praveen Kumar
2018-01-03 11:35   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 15/16 RESEND] rbtree: low level optimizations in rb_erase() Praveen Kumar
2018-01-03 11:37   ` Jan Beulich
2017-11-21 15:20 ` [PATCH v6 16/16 RESEND] rbtree: fix typo in comment of rb_insert_color Praveen Kumar
2018-01-03 11:38   ` Jan Beulich
2017-12-05 16:19 ` [PATCH v6 00/16] xen: common: rbtree: ported updates from Linux tree Praveen Kumar
2017-12-07 15:32   ` Dario Faggioli

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=20171121152009.15591-12-kpraveen.lkml@gmail.com \
    --to=kpraveen.lkml@gmail.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).