All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Malcolm Crossley <malcolm.crossley@citrix.com>
Cc: xen-devel@lists.xenproject.org, keir@xen.org,
	stefano.stabellini@citrix.com, ian.campbell@citrix.com
Subject: Re: [PATCH 2/2] grant_table: convert grant table rwlock to percpu rwlock
Date: Tue, 17 Nov 2015 17:30:59 +0000	[thread overview]
Message-ID: <564B6453.6050008@citrix.com> (raw)
In-Reply-To: <564B6C1A02000078000B603C@prv-mh.provo.novell.com>

On 17/11/15 17:04, Jan Beulich wrote:
>>>> On 03.11.15 at 18:58, <malcolm.crossley@citrix.com> wrote:
>> --- a/xen/common/grant_table.c
>> +++ b/xen/common/grant_table.c
>> @@ -178,6 +178,10 @@ struct active_grant_entry {
>>  #define _active_entry(t, e) \
>>      ((t)->active[(e)/ACGNT_PER_PAGE][(e)%ACGNT_PER_PAGE])
>>  
>> +bool_t grant_rwlock_barrier;
>> +
>> +DEFINE_PER_CPU(rwlock_t *, grant_rwlock);
> Shouldn't these be per grant table? And wouldn't doing so eliminate
> the main limitation of the per-CPU rwlocks?

The grant rwlock is per grant table.

The entire point of this series is to reduce the cmpxchg storm which
happens when many pcpus attempt to grap the same domains grant read lock.

As identified in the commit message, reducing the cmpxchg pressure on
the cache coherency fabric increases intra-vm network through from
10Gbps to 50Gbps when running iperf between two 16-vcpu guests.

Or in other words, 80% of cpu time is wasted with waiting on an atomic
read/modify/write operation against a remote hot cache line.

~Andrew

  reply	other threads:[~2015-11-17 17:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 17:58 [PATCH 1/2] rwlock: add per-cpu reader-writer locks Malcolm Crossley
2015-11-03 17:58 ` [PATCH 2/2] grant_table: convert grant table rwlock to percpu rwlock Malcolm Crossley
2015-11-17 17:04   ` Jan Beulich
2015-11-17 17:30     ` Andrew Cooper [this message]
2015-11-17 17:39       ` Jan Beulich
2015-11-17 17:53         ` Andrew Cooper
2015-11-18  7:45           ` Jan Beulich
2015-11-18 10:06             ` Andrew Cooper
2015-11-18 10:48               ` Jan Beulich
2015-11-18 10:36           ` Ian Campbell
2015-11-18 10:54             ` Jan Beulich
2015-11-18 11:23               ` Malcolm Crossley
2015-11-18 11:41                 ` Jan Beulich
2015-11-18 11:50                   ` Malcolm Crossley
2015-11-18 11:50                 ` Ian Campbell
2015-11-18 11:56                   ` Malcolm Crossley
2015-11-18 12:07                     ` Ian Campbell
2015-11-18 13:08                       ` Malcolm Crossley
2015-11-18 13:47                         ` Jan Beulich
2015-11-18 14:22                         ` Ian Campbell
2015-11-18 20:02       ` Konrad Rzeszutek Wilk
2015-11-19  9:03         ` Malcolm Crossley
2015-11-19 10:09         ` Andrew Cooper
2015-11-05 13:48 ` [PATCH 1/2] rwlock: add per-cpu reader-writer locks Marcos E. Matsunaga
2015-11-05 15:20   ` Malcolm Crossley
2015-11-05 15:46     ` Marcos E. Matsunaga
2015-11-17 17:00 ` Jan Beulich
2015-11-18 13:49   ` Malcolm Crossley
2015-11-18 14:15     ` Jan Beulich
2015-11-18 16:21       ` Malcolm Crossley
2015-11-18 17:04         ` 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=564B6453.6050008@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=malcolm.crossley@citrix.com \
    --cc=stefano.stabellini@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.