Re: [RFC][PATCH 4/4] Rename lock_cpu_hotplug/unlock_cpu_hotplug

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ingo Molnar wrote:
* Nick Piggin <[email protected]> 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.

I agree with you completely.

--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com -
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/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux