Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1219122
| From | Peter Zijlstra <peterz@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression |
| Date | 2015-09-04 17:40 +0200 |
| Message-ID | <q51fP-6d7-9@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <q4TrX-3vn-9@gated-at.bofh.it> <q4UHo-5cD-15@gated-at.bofh.it> <q50MO-5FD-9@gated-at.bofh.it> <q50Wu-5QK-11@gated-at.bofh.it> <q516c-61Z-45@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Sep 04, 2015 at 08:21:28AM -0700, Linus Torvalds wrote: > On Fri, Sep 4, 2015 at 8:14 AM, Peter Zijlstra <peterz@infradead.org> wrote: > > > > The reason we chose to revert to a test-and-set is because regular fair > > locks, like the ticket and the queue thing, have horrible behaviour > > under vcpu preemption. > > Right. However, with our old ticket locks, that's what we got when you > didn't ask for paravirt support. No? Indeed. > And even ignoring the "implementation was crap" issue, some people may > well want their kernels to be "bare hardware" kernels even under a > hypervisor. It may be a slim hypervisor that gives you all the cpus, > or it may just be a system that is just sufficiently overprovisioned, > so you don't get vcpu preemption in practice. Fair enough; I had not considered the slim hypervisor case. Should I place the virt_spin_lock() thing under CONFIG_PARAVIRT (maybe even _SPINLOCKS) such that only paravirt enabled kernels when ran on a hypervisor that does not support paravirt patching (HyperV, VMware, etc..) revert to the test-and-set? > But it would be interesting to hear if just fixing the busy-looping to > not pound the lock with a constant stream of cmpxchg's is already > sufficient to fix the big picture problem. Dave replaced the cpu_relax() with a __delay(1) to match what spinlock-debug does and that fixed things for him. Of course, it would be good if he can try the proposed patch too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[4.2, Regression] Queued spinlocks cause major XFS performance regression Dave Chinner <david@fromorbit.com> - 2015-09-04 07:50 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Linus Torvalds <torvalds@linux-foundation.org> - 2015-09-04 08:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Dave Chinner <david@fromorbit.com> - 2015-09-04 09:20 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Juergen Gross <jgross@suse.com> - 2015-09-04 09:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 10:00 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Dave Chinner <david@fromorbit.com> - 2015-09-04 10:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Linus Torvalds <torvalds@linux-foundation.org> - 2015-09-04 17:10 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 17:20 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 17:30 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Dave Chinner <david@fromorbit.com> - 2015-09-07 01:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Davidlohr Bueso <dave@stgolabs.net> - 2015-09-07 02:10 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-07 09:00 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Linus Torvalds <torvalds@linux-foundation.org> - 2015-09-04 17:30 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 17:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 18:00 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Linus Torvalds <torvalds@linux-foundation.org> - 2015-09-04 18:00 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-05 19:50 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 09:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Peter Zijlstra <peterz@infradead.org> - 2015-09-04 13:40 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Dave Chinner <david@fromorbit.com> - 2015-09-05 00:10 +0200
Re: [4.2, Regression] Queued spinlocks cause major XFS performance regression Dave Chinner <david@fromorbit.com> - 2015-09-07 01:50 +0200
csiph-web