From: Peter Zijlstra <peterz@infradead.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org, Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH] locking/ww_mutex: Replace cpu_relax with cond_resched for tests
Date: Tue, 28 Feb 2017 10:48:53 +0100 [thread overview]
Message-ID: <20170228094853.GF6500@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170228094011.2595-1-chris@chris-wilson.co.uk>
On Tue, Feb 28, 2017 at 09:40:11AM +0000, Chris Wilson wrote:
> When busy-spinning on a ww_mutex_trylock(), we depend upon the other
> thread advancing and releasing the lock. This can not happen on a single
> CPU unless we relinquish it.
Thanks, do you have any clue about those other ww-mutex test fails? So
far I've not had much luck poking at them.
next prev parent reply other threads:[~2017-02-28 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 3:59 [locking/ww_mutex] f2a5fec173 EIP: __mutex_trylock Fengguang Wu
2017-02-28 8:53 ` Chris Wilson
2017-02-28 9:40 ` [PATCH] locking/ww_mutex: Replace cpu_relax with cond_resched for tests Chris Wilson
2017-02-28 9:48 ` Peter Zijlstra [this message]
2017-02-28 9:58 ` Chris Wilson
2017-03-02 8:20 ` [tip:locking/urgent] locking/ww_mutex: Replace cpu_relax() with cond_resched() " tip-bot for Chris Wilson
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=20170228094853.GF6500@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chris@chris-wilson.co.uk \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome