All of lore.kernel.org
 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,
	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 v5 06/17] rbtree: adjust root color in rb_insert_color() only when necessary
Date: Fri, 14 Jul 2017 13:56:25 +0530	[thread overview]
Message-ID: <20170714082636.29511-7-kpraveen.lkml@gmail.com> (raw)
In-Reply-To: <20170714082636.29511-1-kpraveen.lkml@gmail.com>

From: Michel Lespinasse <walken@google.com>

The root node of an rbtree must always be black.  However,
rb_insert_color() only needs to maintain this invariant when it has been
broken - that is, when it exits the loop due to the current (red) node
being the root.  In all other cases (exiting after tree rotations, or
exiting due to an existing black parent) the invariant is already
satisfied, so there is no need to adjust the root node color.

Signed-off-by: Michel Lespinasse <walken@google.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Acked-by: David Woodhouse <David.Woodhouse@intel.com>
Cc: 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 6d58452dc066db61acdff7b84671db1b11a3de1c]

Ported to Xen.

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

diff --git a/xen/common/rbtree.c b/xen/common/rbtree.c
index 1e74ec0f65..16a1a97193 100644
--- a/xen/common/rbtree.c
+++ b/xen/common/rbtree.c
@@ -91,8 +91,21 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 {
 	struct rb_node *parent, *gparent;
 
-	while ((parent = rb_parent(node)) && rb_is_red(parent))
-	{
+	while (true) {
+		/*
+		 * Loop invariant: node is red
+		 *
+		 * If there is a black parent, we are done.
+		 * Otherwise, take some corrective action as we don't
+		 * want a red root or two consecutive red nodes.
+		 */
+		parent = rb_parent(node);
+		if (!parent) {
+			rb_set_black(node);
+			break;
+		} else if (rb_is_black(parent))
+			break;
+
 		gparent = rb_parent(parent);
 
 		if (parent == gparent->rb_left)
@@ -142,8 +155,6 @@ void rb_insert_color(struct rb_node *node, struct rb_root *root)
 			break;
 		}
 	}
-
-	rb_set_black(root->rb_node);
 }
 EXPORT_SYMBOL(rb_insert_color);
 
-- 
2.12.0


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

  parent reply	other threads:[~2017-07-14  8:26 UTC|newest]

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

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=20170714082636.29511-7-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=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 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.