From: Dario Faggioli <dario.faggioli@citrix.com>
To: Malcolm Crossley <malcolm.crossley@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
LarsKurth <lars.kurth@citrix.com>
Subject: Re: [PATCHv2 0/3] Implement per-cpu reader-writer locks
Date: Thu, 26 Nov 2015 10:48:51 +0100 [thread overview]
Message-ID: <1448531331.7833.214.camel@citrix.com> (raw)
In-Reply-To: <56557847.1060707@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1403 bytes --]
[Cc-list edited]
On Wed, 2015-11-25 at 08:58 +0000, Malcolm Crossley wrote:
> On 24/11/15 18:30, George Dunlap wrote:
> > On 24/11/15 18:16, George Dunlap wrote:
> > > On 20/11/15 16:03, Malcolm Crossley wrote:
> > > >
> > > > Removing the cache line bouncing on a multi-socket Haswell-EP
> > > > system
> > > > dramatically improves performance, with 16 vCPU network IO
> > > > performance going
> > > > from 15 gb/s to 64 gb/s! The host under test was fully
> > > > utilising all 40
> > > > logical CPU's at 64 gb/s, so a bigger logical CPU host may see
> > > > an even better
> > > > IO improvement.
> > >
> > > Impressive -- thanks for doing this work.
>
> Thanks, I think the key to isolating the problem was using profiling
> tools. The scale
> of the overhead would not have been clear without them.
>
As an aside, if it's not too much work, a few hints and instruction on
how such profiling has been done would be helpful for others and for
the future.
For example, a post on The Xen Project's blog about that (that then can
be turned into a wiki page) would be awesome. :-)
Regards,
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-26 9:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 16:03 [PATCHv2 0/3] Implement per-cpu reader-writer locks Malcolm Crossley
2015-11-20 16:03 ` [PATCHv2 1/3] rwlock: Add " Malcolm Crossley
2015-11-25 11:12 ` George Dunlap
2015-11-26 12:17 ` Jan Beulich
2015-11-20 16:03 ` [PATCHv2 2/3] grant_table: convert grant table rwlock to percpu rwlock Malcolm Crossley
2015-11-25 12:35 ` Jan Beulich
2015-11-25 13:43 ` Malcolm Crossley
2015-11-25 13:53 ` Jan Beulich
2015-11-25 14:11 ` Malcolm Crossley
2015-11-20 16:03 ` [PATCHv2 3/3] p2m: " Malcolm Crossley
2015-11-25 12:00 ` George Dunlap
2015-11-25 12:38 ` Jan Beulich
2015-11-25 12:54 ` Malcolm Crossley
2015-11-24 18:16 ` [PATCHv2 0/3] Implement per-cpu reader-writer locks George Dunlap
2015-11-24 18:30 ` George Dunlap
2015-11-25 8:58 ` Malcolm Crossley
2015-11-25 9:49 ` George Dunlap
2015-11-26 9:48 ` Dario Faggioli [this message]
2015-11-24 18:32 ` Andrew Cooper
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=1448531331.7833.214.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@citrix.com \
--cc=lars.kurth@citrix.com \
--cc=malcolm.crossley@citrix.com \
--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 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.