public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: balbir@linux.vnet.ibm.com
Cc: Ingo Molnar <mingo@elte.hu>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
	Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
	Dhaval Giani <dhaval@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Make yield_task_fair more efficient
Date: Thu, 21 Feb 2008 12:12:54 +0100	[thread overview]
Message-ID: <1203592374.6243.138.camel@lappy> (raw)
In-Reply-To: <47BD4D48.4080606@linux.vnet.ibm.com>


On Thu, 2008-02-21 at 15:37 +0530, Balbir Singh wrote:

> You use the empty pointer (missing right child), so why do we need a list. May
> be I am missing something.

A fully threaded tree also has back-pointer to traverse backwards
through the ordered elements.

That said, overloading the right child pointer might not be the best
thing for the linux kernel, as it will impact all the rb-tree lookups
which are open-coded and often performance critical (this is the reason
the colour isn't bit encoded in either of the child pointers either).

But if you only want a uni directional thread, I guess we can stick it
in the unsigned long we use for the node colour.

Still, perhaps it's worth it to grow rb_node to 4 words and do the fully
threaded thing as there are also a lot of rb_prev() users in the kernel.
Who knows..

Anyway, I agree that improving rb_next() is worth looking into for the
scheduler.



  reply	other threads:[~2008-02-21 11:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  5:33 Make yield_task_fair more efficient Balbir Singh
2008-02-21  6:04 ` Ingo Molnar
2008-02-21  6:51   ` Balbir Singh
2008-02-21  7:07     ` Ingo Molnar
2008-02-21  7:39       ` Balbir Singh
2008-02-21  8:43         ` Peter Zijlstra
2008-02-21  8:50           ` Balbir Singh
2008-02-21  9:04             ` Ingo Molnar
2008-02-21  9:31               ` Balbir Singh
2008-02-21  9:42                 ` Ingo Molnar
2008-02-21  9:44                   ` Balbir Singh
2008-02-21  9:43                 ` Peter Zijlstra
2008-02-21  9:42                   ` Balbir Singh
2008-02-21 10:01                     ` Peter Zijlstra
2008-02-21 10:07                       ` Balbir Singh
2008-02-21 11:12                         ` Peter Zijlstra [this message]
2008-02-21 11:27                           ` Balbir Singh
2008-02-21 20:38                           ` Jens Axboe
2008-02-21 20:55                             ` Jens Axboe
2008-02-22  3:27                               ` Balbir Singh
2008-02-21 10:17                 ` Balbir Singh
2008-02-21 12:02                 ` Mike Galbraith
2008-02-21 12:06                   ` Mike Galbraith
2008-02-21 13:29                   ` Balbir Singh
2008-02-21 14:38     ` Jörn Engel

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=1203592374.6243.138.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@linux.vnet.ibm.com \
    --cc=yanmin_zhang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox