Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762031AbYBUKMQ (ORCPT ); Thu, 21 Feb 2008 05:12:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757203AbYBUKL7 (ORCPT ); Thu, 21 Feb 2008 05:11:59 -0500 Received: from E23SMTP06.au.ibm.com ([202.81.18.175]:43725 "EHLO e23smtp06.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756195AbYBUKL5 (ORCPT ); Thu, 21 Feb 2008 05:11:57 -0500 Message-ID: <47BD4D48.4080606@linux.vnet.ibm.com> Date: Thu, 21 Feb 2008 15:37:04 +0530 From: Balbir Singh Reply-To: balbir@linux.vnet.ibm.com Organization: IBM User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Peter Zijlstra CC: Ingo Molnar , "Zhang, Yanmin" , Srivatsa Vaddagiri , Dhaval Giani , linux-kernel@vger.kernel.org Subject: Re: Make yield_task_fair more efficient References: <20080221053321.GA26918@balbir.in.ibm.com> <20080221060427.GA9159@elte.hu> <47BD1F75.5030506@linux.vnet.ibm.com> <20080221070733.GA13694@elte.hu> <47BD2A99.3010608@linux.vnet.ibm.com> <1203583439.6243.119.camel@lappy> <47BD3B56.3090404@linux.vnet.ibm.com> <20080221090430.GA20055@elte.hu> <47BD44FF.7070104@linux.vnet.ibm.com> <1203586980.6243.124.camel@lappy> <47BD479F.6070901@linux.vnet.ibm.com> <1203588090.6243.128.camel@lappy> In-Reply-To: <1203588090.6243.128.camel@lappy> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1764 Lines: 50 Peter Zijlstra wrote: > On Thu, 2008-02-21 at 15:12 +0530, Balbir Singh wrote: >> Peter Zijlstra wrote: >>> On Thu, 2008-02-21 at 15:01 +0530, Balbir Singh wrote: >>> >>>> I have an alternate approach in mind (that I need to find time for), >>>> threaded-rbtrees. Walking the tree is really efficient, specially finding >>>> successor of a node. >>> Threading the rbtrees would be even more expensive, it would require a >>> list_head in each node and a full list operation for every tree >>> operation. >>> >> Peter, when I say threaded, I don't mean threaded as in tasks. Please see >> http://www.nist.gov/dads/HTML/threadedtree.html and >> http://datastructures.itgo.com/trees/tbt.htm > > I'm quite aware of the meaning of threaded in the context of data > structures. Oh! I did not mean to assume anything. Just wanted to make sure we are talking of the same thing They usually require additional list data and operations to > implement. > >From the definition A Threaded Binary Tree is a binary tree in which every node that does not have a right child has a THREAD (in actual sense, a link) to its INORDER successor. You use the empty pointer (missing right child), so why do we need a list. May be I am missing something. > Look at how the latter link you provided grows the rb_node with one > pointer to provide a single linked list. > Yes, that's a bad example I suppose. Look at http://www.cs.rutgers.edu/~kaplan/503/thread.html -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/