From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: kurt.hackel@oracle.com, boris.ostrovsky@oracle.com,
xen-devel@lists.xensource.com
Subject: Re: Linux v3.12 + pv ticketlocks.
Date: Thu, 12 Sep 2013 21:44:46 -0700 [thread overview]
Message-ID: <5232983E.2030402@goop.org> (raw)
In-Reply-To: <1378723192.19967.41.camel@kazak.uk.xensource.com>
On 09/09/2013 03:39 AM, Ian Campbell wrote:
> On Fri, 2013-09-06 at 16:11 -0400, Konrad Rzeszutek Wilk wrote:
>> Hey,
>>
>> Linux v3.12 (which is now in merge window phase) has the code for
>> making the spinlock use ticketlocks for everything.
> Congrats!
Yeah! Lots of good work to turn my stuff into something submittable. I
got stalled by the wall of perf testing.
>> Majority of that work was done by Jeremy Fitzhardinge and I would like
>> to thank him for doing this work. It had taken a year (or more) to actually
> Way more that a year, wasn't it? This stuff has been floating around for
> 3 or 4 years or longer IIRC.
Not quite - the timestamps in my git tree are mid 2010-2011. I did the
first pv spinlocks at the Xen summit with the paper, which was about
2008? 9?
J
>
> BTW Attilio Rao did some upstreaming work and a bunch of measurement
> stuff too.
>
> Ian.
>
next prev parent reply other threads:[~2013-09-13 4:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 20:11 Linux v3.12 + pv ticketlocks Konrad Rzeszutek Wilk
2013-09-09 10:39 ` Ian Campbell
2013-09-09 14:03 ` Konrad Rzeszutek Wilk
2013-09-10 17:41 ` Dario Faggioli
2013-09-11 19:03 ` Konrad Rzeszutek Wilk
2013-09-13 15:17 ` Dario Faggioli
2013-09-13 4:44 ` Jeremy Fitzhardinge [this message]
2013-09-11 18:25 ` Sander Eikelenboom
2013-09-11 18:41 ` Konrad Rzeszutek Wilk
2013-09-11 19:05 ` Sander Eikelenboom
2013-09-11 19:24 ` Konrad Rzeszutek Wilk
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=5232983E.2030402@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.