On Fri, Aug 25, 2006 at 04:19:29PM +1000, Nick Piggin wrote: > Well you would just have a depth count in the task_struct... That (if can have) would make life so easy :) -- Regards, vatsa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Gautham R Shenoy <[email protected]>
- Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Ingo Molnar <[email protected]>
- Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Gautham R Shenoy <[email protected]>
- Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Ingo Molnar <[email protected]>
- Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Srivatsa Vaddagiri <[email protected]>
- Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Gautham R Shenoy <[email protected]>
- Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- From: Nick Piggin <[email protected]>
- [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- Prev by Date: Re: [Bug] 2.6.18-rc4-mm2 panic in __unix_insert_socket x86_64
- Next by Date: Re: [PATCH] BLOCK: Make it possible to disable the block layer
- Previous by thread: Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- Next by thread: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug
- Index(es):
 |