Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1589318 > unrolled thread

Re: [PATCH] locking/ww_mutex: Replace cpu_relax with cond_resched for tests

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] locking/ww_mutex: Replace cpu_relax with cond_resched  for tests Peter Zijlstra <peterz@infradead.org> - 2017-02-28 10:50 +0100
    Re: [PATCH] locking/ww_mutex: Replace cpu_relax with cond_resched  for tests Chris Wilson <chris@chris-wilson.co.uk> - 2017-02-28 11:00 +0100

#1589318 — Re: [PATCH] locking/ww_mutex: Replace cpu_relax with cond_resched for tests

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.

[toc] | [next] | [standalone]

#1589326

On Tue, Feb 28, 2017 at 10:48:53AM +0100, Peter Zijlstra wrote:
> 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.

Not yet, they didn't seem quite so self-explanatory as this trace :(
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web