From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Matt Wilson <msw@linux.com>
Cc: "Felipe Franciosi" <felipe.franciosi@citrix.com>,
"Anthony Liguori" <aliguori@amazon.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Keir Fraser" <keir.xen@gmail.com>,
"David Vrabel" <david.vrabel@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
xen-devel@lists.xenproject.org, "Matt Wilson" <msw@amazon.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [RFC PATCH 2/2] gnttab: refactor locking for better scalability
Date: Tue, 12 Nov 2013 09:52:57 -0500 [thread overview]
Message-ID: <20131112145257.GD9435@phenom.dumpdata.com> (raw)
In-Reply-To: <20131112071857.GA11872@u109add4315675089e695.ant.amazon.com>
> I should also mention that some of the improvement I mentioned from
> 3,000 MB/s to 3,600 MB/s was due to avoiding the m2p override spinlock
> in dom0.
Could you post said patch please? I presume its pretty simple but
I would like the credit to go to you guys.
next prev parent reply other threads:[~2013-11-12 14:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 2:03 [RFC PATCH 0/2] gnttab: refactor locking for better scalability Matt Wilson
2013-11-12 2:03 ` [RFC PATCH 1/2] gnttab: lock the local grant table earlier in __gnttab_unmap_common() Matt Wilson
2013-11-12 2:03 ` [RFC PATCH 2/2] gnttab: refactor locking for better scalability Matt Wilson
2013-11-12 5:37 ` Keir Fraser
2013-11-12 7:18 ` Matt Wilson
2013-11-12 8:07 ` Keir Fraser
2013-11-12 9:18 ` Jan Beulich
2013-11-12 13:42 ` Keir Fraser
2013-11-12 13:58 ` Keir Fraser
2013-11-12 14:11 ` Jan Beulich
2013-11-12 14:24 ` Keir Fraser
2013-11-12 15:09 ` Felipe Franciosi
2014-06-20 20:54 ` Konrad Rzeszutek Wilk
2014-06-20 21:18 ` Matt Wilson
2013-11-12 19:06 ` Matt Wilson
2013-11-12 14:52 ` Konrad Rzeszutek Wilk [this message]
2013-11-12 15:04 ` David Vrabel
2013-11-12 16:53 ` Anthony Liguori
2013-11-12 9:26 ` Jan Beulich
2013-11-12 17:58 ` Matt Wilson
2013-11-13 7:39 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2014-06-21 0:13 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=20131112145257.GD9435@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=aliguori@amazon.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=felipe.franciosi@citrix.com \
--cc=keir.xen@gmail.com \
--cc=msw@amazon.com \
--cc=msw@linux.com \
--cc=roger.pau@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.