All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <chegger@amazon.de>
To: xen-devel@lists.xen.org
Cc: Christoph Egger <chegger@amazon.de>
Subject: [PATCH v4 0/2] gnttab: Improve scaleability
Date: Fri, 9 Jan 2015 16:12:03 +0100	[thread overview]
Message-ID: <1420816325-26738-1-git-send-email-chegger@amazon.de> (raw)

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.

v4:
  * Coding style nits from Jan Beulich
  * Fixup read locks pointed out by Jan Beulich
  * renamed double_gt_(un)lock to double_maptrack_(un)lock
    per request from Jan Beulich
  * Addressed ASSERT()'s from Jan Beulich

v3:
  * Addressed gnttab_swap_grant_ref() comment from Andrew Cooper
v2:
  * Add arm part per request from Julien Grall

Christoph Egger (1):
  gnttab: Introduce rwlock to protect updates to grant table state

Matt Wilson (1):
  gnttab: refactor locking for scalability

 docs/misc/grant-tables.txt    |   49 ++++++-
 xen/arch/arm/mm.c             |    4 +-
 xen/arch/x86/mm.c             |    4 +-
 xen/common/grant_table.c      |  321 +++++++++++++++++++++++++----------------
 xen/include/xen/grant_table.h |    9 +-
 5 files changed, 258 insertions(+), 129 deletions(-)

-- 
1.7.9.5

             reply	other threads:[~2015-01-09 15:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 15:12 Christoph Egger [this message]
2015-01-09 15:12 ` [PATCH v4 1/2] gnttab: Introduce rwlock to protect updates to grant table state Christoph Egger
2015-01-12 15:09   ` Jan Beulich
2015-01-12 16:03     ` Egger, Christoph
2015-01-12 16:22       ` Jan Beulich
2015-01-09 15:12 ` [PATCH v4 2/2] gnttab: refactor locking for scalability Christoph Egger
2015-01-12 15:25   ` Jan Beulich

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=1420816325-26738-1-git-send-email-chegger@amazon.de \
    --to=chegger@amazon.de \
    --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.