From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>, Matt Wilson <msw@amazon.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Hackathon minutes] PV block improvements
Date: Tue, 25 Jun 2013 18:30:17 +0200 [thread overview]
Message-ID: <51C9C599.2030900@citrix.com> (raw)
In-Reply-To: <1372175878.18901.62.camel@zakaz.uk.xensource.com>
On 25/06/13 17:57, Ian Campbell wrote:
> On Sat, 2013-06-22 at 09:11 +0200, Roger Pau Monné wrote:
>> First because grant_copy is done by the hypervisor, while when using
>> persistent grants the copy is done by the guest.
>
> This is true and a reasonable concern.
>
>> Also, grant_copy takes
>> the grant lock, so when scaling to a large number of domains there's
>> going to be contention around this lock.
>
> Does grant copy really take the lock for the duration of the copy,
> preventing any other grant ops from the source and/or target domain?
>
> If true then that sounds like an area which is ripe for optimisation!
>
> However I am hopeful that you are mistaken... __acquire_grant_for_copy()
> takes the grant lock while it pins the entry into the active grant entry
> list and not for the actual duration of the copy (and likewise
> __release_grant_for-copy). I hope Jan can confirm this!
Sorry, probably I haven't detailed enough here. I didn't want to mean it
takes the lock for the duration of the whole copy, but it is used at
some places during the grant copy operation so it might introduce
contention when the number of domains is high (although I have not
measured it).
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-06-25 16:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 15:06 [Hackathon minutes] PV block improvements Roger Pau Monné
2013-06-21 17:10 ` Roger Pau Monné
2013-06-21 18:07 ` Matt Wilson
2013-06-22 7:11 ` Roger Pau Monné
2013-06-25 6:09 ` Matt Wilson
2013-06-25 13:01 ` Wei Liu
2013-06-25 15:39 ` Matt Wilson
2013-06-25 15:53 ` Ian Campbell
2013-06-25 18:04 ` Stefano Stabellini
2013-06-26 9:37 ` George Dunlap
2013-06-26 11:37 ` Ian Campbell
2013-06-27 13:58 ` George Dunlap
2013-06-27 14:21 ` Ian Campbell
2013-06-27 15:20 ` Roger Pau Monné
2013-06-25 15:57 ` Ian Campbell
2013-06-25 16:05 ` Jan Beulich
2013-06-25 16:30 ` Roger Pau Monné [this message]
2013-06-27 15:12 ` Roger Pau Monné
2013-06-27 15:26 ` Stefano Stabellini
2013-06-21 20:16 ` Konrad Rzeszutek Wilk
2013-06-21 23:17 ` Wei Liu
2013-06-24 11:06 ` Stefano Stabellini
2013-07-02 11:49 ` Roger Pau Monné
2013-06-22 7:17 ` Roger Pau Monné
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=51C9C599.2030900@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=msw@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).