All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <richardw.yang@linux.intel.com>
To: Michel Lespinasse <walken@google.com>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Davidlohr Bueso <dbueso@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch v2 1/2] lib/rbtree: set successor's parent unconditionally
Date: Mon, 28 Oct 2019 14:23:58 +0800	[thread overview]
Message-ID: <20191028062358.GA13412@richard> (raw)
In-Reply-To: <CANN689FNPD1U+gGaO5PmCuMULvkzOffOAPuB8fmyhVLHSqM7Vw@mail.gmail.com>

On Sun, Oct 27, 2019 at 09:29:43PM -0700, Michel Lespinasse wrote:
>Code looks fine, for both commits in this series. Please make sure to
>double check that lib/rbtree_test does not show any performance
>regressions, but assuming they don't, looks great !
>

Thanks :-)

>Reviewed-By: Michel Lespinasse <walken@google.com>
>
>On Sun, Oct 27, 2019 at 7:15 PM Wei Yang <richardw.yang@linux.intel.com> wrote:
>>
>> Both in Case 2 and 3, we exchange n and s. This mean no matter whether
>> child2 is NULL or not, successor's parent should be assigned to node's.
>>
>> This patch takes this step out to make it explicit and reduce the
>> ambiguity.
>>
>> Besides, this step reduces some symbol size like rb_erase().
>>
>>    KERN_CONFIG       upstream       patched
>>    OPT_FOR_PERF      877            870
>>    OPT_FOR_SIZE      635            621
>>
>> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
>> ---
>>  include/linux/rbtree_augmented.h | 3 +--
>>  1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/include/linux/rbtree_augmented.h b/include/linux/rbtree_augmented.h
>> index fdd421b8d9ae..99c42e1a74b8 100644
>> --- a/include/linux/rbtree_augmented.h
>> +++ b/include/linux/rbtree_augmented.h
>> @@ -283,14 +283,13 @@ __rb_erase_augmented(struct rb_node *node, struct rb_root *root,
>>                 __rb_change_child(node, successor, tmp, root);
>>
>>                 if (child2) {
>> -                       successor->__rb_parent_color = pc;
>>                         rb_set_parent_color(child2, parent, RB_BLACK);
>>                         rebalance = NULL;
>>                 } else {
>>                         unsigned long pc2 = successor->__rb_parent_color;
>> -                       successor->__rb_parent_color = pc;
>>                         rebalance = __rb_is_black(pc2) ? parent : NULL;
>>                 }
>> +               successor->__rb_parent_color = pc;
>>                 tmp = successor;
>>         }
>>
>> --
>> 2.17.1
>>
>
>
>-- 
>Michel "Walken" Lespinasse
>A program is never fully debugged until the last user dies.

-- 
Wei Yang
Help you, Help me

  reply	other threads:[~2019-10-28  6:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28  2:14 [Patch v2 1/2] lib/rbtree: set successor's parent unconditionally Wei Yang
2019-10-28  2:14 ` [Patch v2 2/2] lib/rbtree: get successor's color directly Wei Yang
2019-10-28  9:21   ` Peter Zijlstra
2019-10-28  4:29 ` [Patch v2 1/2] lib/rbtree: set successor's parent unconditionally Michel Lespinasse
2019-10-28  6:23   ` Wei Yang [this message]
2019-10-28  9:20 ` Peter Zijlstra

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=20191028062358.GA13412@richard \
    --to=richardw.yang@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=dbueso@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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.