[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060927090524.GA20395@elte.hu>
Date:	Wed, 27 Sep 2006 11:05:24 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Bill Huey <billh@...ppy.monkey.org>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	John Stultz <johnstul@...ibm.com>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Dipankar Sarma <dipankar@...ibm.com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] move put_task_struct() reaping into a thread [Re: 2.6.18-rt1]
* Bill Huey <billh@...ppy.monkey.org> wrote:
> > more than just changing locking behavior.  Which is what brought me 
> > into this conversation in the first place.  So removing that point 
> > of discord would be good.
> 
> Yes, there are few places. It was primarily to handle the reaping 
> during the finishing parts of a fork. All in all, it's not at all a 
> critical path.
no. It was primarily to move the put_task_struct() off the 
context-switch fastpath. (In comparison the fork use is much rarer)
	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
