Re: [PATCH v4 1/3] qspinlock: Introducing a 4-byte queue spinlock implementation

From: Peter Zijlstra
Date: Tue Feb 18 2014 - 16:38:15 EST


On Tue, Feb 18, 2014 at 02:39:31PM -0500, Waiman Long wrote:
> >>+ /*
> >>+ * At the head of the wait queue now
> >>+ */
> >>+ while (true) {
> >>+ u32 qcode;
> >>+ int retval;
> >>+
> >>+ retval = queue_get_lock_qcode(lock,&qcode, my_qcode);
> >>+ if (retval> 0)
> >>+ ; /* Lock not available yet */
> >>+ else if (retval< 0)
> >>+ /* Lock taken, can release the node& return */
> >>+ goto release_node;
> >>+ else if (qcode != my_qcode) {
> >>+ /*
> >>+ * Just get the lock with other spinners waiting
> >>+ * in the queue.
> >>+ */
> >>+ if (queue_spin_trylock_unfair(lock))
> >>+ goto notify_next;
> >Why is this an option at all?
> >
> >
>
> Are you referring to the case (qcode != my_qcode)? This condition will be
> true if more than one tasks have queued up.

But in no case should we revert to unfair spinning or stealing. We
should always respect the queueing order.

If the lock tail no longer points to us, then there's further waiters
and we should wait for ->next and unlock it -- after we've taken the
lock.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/