* Steven Rostedt <[email protected]> wrote:
> OK, I'm declaring defeat here. I've been fighting race conditions all
> day, and it's now 1 in the morning where I live. It looks like this
> implementation has no other choice but to have the waking up "pending
> owner" take the wait_list lock once again. How heavy of a overhead is
> that really?
as i mentioned it before, taking a lock is not a big issue at all. Since
you have to touch the lock data structure anyway (and all of it fits
into a single cacheline), it doesnt really matter whether it's atomic
flag setting/clearing, or raw spinlock based.
later on, once things are stable and well-understood, we can still
attempt to micro-optimize it.
Ingo
-
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]
