From: "Egger, Christoph" <chegger@amazon.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/2] gnttab: Improve scaleability
Date: Tue, 2 Dec 2014 12:08:06 +0100 [thread overview]
Message-ID: <547D9D96.2090700@amazon.de> (raw)
In-Reply-To: <547D9BB9.7010305@citrix.com>
On 2014/12/02 12:00, Andrew Cooper wrote:
> On 02/12/14 10:06, Christoph Egger wrote:
>> This patch series changes the grant table locking to
>> a more fain grained locking protocol. The result is
>> a performance boost measured with blkfront/blkback.
>> Document the locking protocol.
>>
>> [PATCH 1/2] gnttab: Introduce rwlock to protect updates to grant
>> [PATCH 2/2] gnttab: refactor locking for scalability
>
> XenServer has been using the original version of this patch
Maybe the one sent by Matt Wilson some time ago?
> (forward ported a little),
This version is against staging tree.
> and it makes significant improvements to our scalability.
Thanks for confirmation.
> I highly recommend this for inclusion, although for 4.6 at this point.
I am fine with this. I would be happy to see a backport to xen 4.5 and
4.4 then.
Christoph
prev parent reply other threads:[~2014-12-02 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 10:06 [PATCH 0/2] gnttab: Improve scaleability Christoph Egger
2014-12-02 10:06 ` [PATCH 1/2] gnttab: Introduce rwlock to protect updates to grant table state Christoph Egger
2014-12-02 11:28 ` Andrew Cooper
2014-12-02 12:35 ` Julien Grall
2014-12-02 13:03 ` Egger, Christoph
2014-12-02 13:08 ` Julien Grall
2014-12-02 13:18 ` Egger, Christoph
2014-12-02 10:06 ` [PATCH 2/2] gnttab: refactor locking for scalability Christoph Egger
2014-12-02 11:00 ` [PATCH 0/2] gnttab: Improve scaleability Andrew Cooper
2014-12-02 11:08 ` Egger, Christoph [this message]
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=547D9D96.2090700@amazon.de \
--to=chegger@amazon.de \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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.