xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com,
	Ian Campbell <Ian.Campbell@citrix.com>,
	kurt.hackel@oracle.com,
	Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
	boris.ostrovsky@oracle.com
Subject: Re: Linux v3.12 + pv ticketlocks.
Date: Tue, 10 Sep 2013 19:41:04 +0200	[thread overview]
Message-ID: <1378834864.2821.52.camel@Solace> (raw)
In-Reply-To: <20130909140314.GI21435@phenom.dumpdata.com>


[-- Attachment #1.1: Type: text/plain, Size: 1497 bytes --]

On lun, 2013-09-09 at 10:03 -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Sep 09, 2013 at 11:39:52AM +0100, Ian Campbell wrote:
>
> > Congrats!
> 
Huge to everyone that has been involved in it congrats from me too! :-)

> Thank you. Albeit most of the credit goes to folks you and me mentioned
> and as well Raghavendra K T for tirelessly picking it up and
> upstreaming it.
> 
> > 
> > > 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
> > 
>
> > 
> > BTW Attilio Rao did some upstreaming work and a bunch of measurement
> > stuff too.
> 
> And a nice Wiki entry:
> 
> http://wiki.xen.org/wiki/Benchmarking_the_new_PV_ticketlock_implementation
> 
> and an awesome blog entry:
> http://blog.xen.org/index.php/2012/05/11/benchmarking-the-new-pv-ticketlock-implementation/
> 
Indeed. Still, the fact that the code finally hit upstream, certainly
calls for another blog post! :-)

For example, it would be nice to make an announcement that this is now
upstreamed and also, if I understood your patches correctly, available
for all the virtualization modes we support!

Anyone up for it?

Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-09-10 17:41 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 [this message]
2013-09-11 19:03       ` Konrad Rzeszutek Wilk
2013-09-13 15:17         ` Dario Faggioli
2013-09-13  4:44   ` Jeremy Fitzhardinge
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=1378834864.2821.52.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=kurt.hackel@oracle.com \
    --cc=raghavendra.kt@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).