From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Ding Tianhong <dingtianhong@huawei.com>,
Jason Low <jason.low2@hpe.com>,
Davidlohr Bueso <dave@stgolabs.net>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <Will.Deacon@arm.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
Imre Deak <imre.deak@intel.com>
Subject: Re: [PATCH v4 2/3] locking/mutex: Enable optimistic spinning of woken task in wait queue
Date: Mon, 8 Aug 2016 19:29:38 +0200 [thread overview]
Message-ID: <20160808172938.GY6862@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1468874366-56955-3-git-send-email-Waiman.Long@hpe.com>
On Mon, Jul 18, 2016 at 04:39:25PM -0400, Waiman Long wrote:
> Ding Tianhong reported a live-lock situation where a constant stream
> of incoming optimistic spinners blocked a task in the wait list from
> getting the mutex.
>
> This patch attempts to fix this live-lock condition by enabling the
> woken task in the wait queue to enter into an optimistic spinning
> loop itself in parallel with the regular spinners in the OSQ. This
> should prevent the live-lock condition from happening.
No, two spinners are not in fact starvation proof. It makes the reported
life-lock scenario much less likely, but it does not guarantee anything.
> + /*
> + * Optimistically spinning on the mutex without the wait lock
There should either be a '.' at the end of that line, or the next line
should not start with a capital.
Also, I don't see how the two sentences are related, should they be in
the same paragraph?
> + * The state has to be set to running to avoid another waker
> + * spinning on the on_cpu flag while the woken waiter is
> + * spinning on the mutex.
> + */
> + acquired = mutex_optimistic_spin(lock, ww_ctx, use_ww_ctx,
> + true);
> spin_lock_mutex(&lock->wait_lock, flags);
> }
> __set_task_state(task, TASK_RUNNING);
next prev parent reply other threads:[~2016-08-08 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 20:39 [PATCH v4 0/3] locking/mutex: Enable optimistic spinning of lock waiter Waiman Long
2016-07-18 20:39 ` [PATCH v4 1/3] locking/mutex: Add waiter parameter to mutex_optimistic_spin() Waiman Long
2016-08-08 17:26 ` Peter Zijlstra
2016-08-09 17:36 ` Waiman Long
2016-07-18 20:39 ` [PATCH v4 2/3] locking/mutex: Enable optimistic spinning of woken task in wait queue Waiman Long
2016-08-08 17:29 ` Peter Zijlstra [this message]
2016-08-09 17:49 ` Waiman Long
2016-07-18 20:39 ` [PATCH v4 3/3] locking/mutex: Ensure forward progress of waiter-spinner Waiman Long
2016-08-08 17:37 ` Peter Zijlstra
2016-08-09 18:00 ` Waiman Long
2016-08-10 9:29 ` Peter Zijlstra
2016-08-10 17:51 ` Waiman Long
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160808172938.GY6862@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Waiman.Long@hpe.com \
--cc=Will.Deacon@arm.com \
--cc=dave@stgolabs.net \
--cc=dingtianhong@huawei.com \
--cc=imre.deak@intel.com \
--cc=jason.low2@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox