From: Peter Zijlstra <peterz@infradead.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: mingo@kernel.org, kvm@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Waiman.Long@hpe.com,
dhowells@redhat.com, david.vrabel@citrix.com,
pbonzini@redhat.com, xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH] x86, locking: Remove ticket (spin)lock implementation
Date: Wed, 18 May 2016 21:34:31 +0200 [thread overview]
Message-ID: <20160518193431.GQ3193@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160518191344.GA9101@char.us.oracle.com>
On Wed, May 18, 2016 at 03:13:44PM -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, May 18, 2016 at 08:43:02PM +0200, Peter Zijlstra wrote:
> >
> > We've unconditionally used the queued spinlock for many releases now.
>
> Like since 4.2?
Yeah, that seems to be the right number.
> I don't know of any enterprise distro that is shipping anything
> more modern than 4.1?
RHEL 7 -- v3.10
SLES 12 -- v3.12
Debian Jessie -- v3.16
Ubuntu 16.04 LTS -- v4.4
But waiting for the major enterprise distros (RHEL/SLES) would mean
another decade or so before people start using it. We don't usually wait
this long for anything.
> Perhaps it would be good to wait until they
> at least ship and then give them some time to see if they have found
> any issues?
My motivation was that people keep trying to send patches against the
ticket lock code... David did just today, and he's not the first.
next prev parent reply other threads:[~2016-05-18 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 18:43 [PATCH] x86,locking: Remove ticket (spin)lock implementation Peter Zijlstra
2016-05-18 19:13 ` [Xen-devel] [PATCH] x86, locking: " Konrad Rzeszutek Wilk
2016-05-18 19:34 ` Peter Zijlstra [this message]
2016-05-19 7:16 ` Ingo Molnar
2016-05-19 10:52 ` Paolo Bonzini
2016-05-19 9:07 ` [PATCH] x86,locking: " David Vrabel
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=20160518193431.GQ3193@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Waiman.Long@hpe.com \
--cc=david.vrabel@citrix.com \
--cc=dhowells@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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