Messages in this thread | | | Date | Thu, 24 Aug 2006 17:00:26 +0200 | From | Ingo Molnar <> | Subject | Re: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug |
| |
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> It really is just like a reentrant rw semaphore... I don't see the > point of the name change, but I guess we don't like reentrant locks so > calling it something else might go down better with Linus ;)
what would fit best is a per-cpu scalable (on the read-side) self-reentrant rw mutex. We are doing cpu hotplug locking in things like fork or the slab code, while most boxes will do a CPU hotplug event only once in the kernel's lifetime (during bootup), so a classic global read-write lock is unjustified.
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/
| |