[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060921065402.GA22089@elte.hu>
Date: Thu, 21 Sep 2006 08:54:02 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Bill Huey <billh@...ppy.monkey.org>
Cc: 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:
> On Wed, Sep 20, 2006 at 04:19:07PM +0200, Ingo Molnar wrote:
> > I'm pleased to announce the 2.6.18-rt1 tree, which can be downloaded
> > from the usual place:
> ...
> > as usual, bugreports, fixes and suggestions are welcome,
>
> Speaking of which...
>
> This patch moves put_task_struct() reaping into a thread instead of an
> RCU callback function [...]
had some time to think about it since yesterday: RCU reaping is done in
softirqs (check out the softirq-rcu threads on your -rt box), that's why
i removed the delayed-task-drop code to begin with. Now i dont doubt
that you saw crashes under 2.6.17 - but did you manage to figure out
what the reason is for those crashes, and do those reasons really
necessiate the pushing of task-reapdown into yet another set of kernel
threads?
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