Date: Mon, 31 Oct 2005 22:44:49 +0100
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, tytso@us.ibm.com, sripathi@in.ibm.com,
       dipankar@in.ibm.com, oleg@tv-sign.ru
Subject: Re: [RFC,PATCH] RCUify single-thread case of clock_gettime()
Message-ID: <20051031214449.GB17489@elte.hu>
References: <20051031174416.GA2762@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051031174416.GA2762@us.ibm.com>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 958
Lines: 26


* Paul E. McKenney <paulmck@us.ibm.com> wrote:

> Hello!
> 
> The attached patch uses RCU to avoid the need to acquire tasklist_lock 
> in the single-thread case of clock_gettime().  Still acquires 
> tasklist_lock when asking for the time of a (potentially 
> multithreaded) process.
> 
> Experimental, has been touch-tested on x86 and POWER.  Requires RCU on 
> task_struct.  Further more focused testing in progress.
> 
> Thoughts?  (Why?  Some off-list users want to be able to monitor CPU 
> consumption of specific threads.  They need to do so quite frequently, 
> so acquiring tasklist_lock is inappropriate.)

looks good to me - i have added this to the -rt tree, it should show up 
in 2.6.14-rt3.

	Ingo
-
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/