All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: <xen-devel@lists.xen.org>, <linux-kernel@vger.kernel.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Xen-devel] [PATCH RFC] p2m: use GNTTABOP_unmap_and_duplicate if	available
Date: Thu, 1 Aug 2013 12:21:32 +0200	[thread overview]
Message-ID: <51FA36AC.1090609@citrix.com> (raw)
In-Reply-To: <51FA302B.90106@citrix.com>

On 01/08/13 11:53, David Vrabel wrote:
> On 31/07/13 17:07, Roger Pau Monne wrote:
>> The new GNTTABOP_unmap_and_duplicate operation doesn't zero the
>> mapping passed in new_addr, allowing us to perform batch unmaps in p2m
>> code without requiring the use of a multicall.
> 
> Thanks. This looks like it should be a good performance improvement for
> userspace-based backends.  Do you have any performance measurements for
> (e.g.) qemu's disk backend?

Not yet, I might be able to get some initial performance measurements
tomorrow.

> 
>> --- a/arch/x86/xen/p2m.c
>> +++ b/arch/x86/xen/p2m.c
> [...]
>> +int m2p_remove_override_batch(struct page **pages,
>> +		struct gnttab_map_grant_ref *kmap_ops, int count)
>> +{
> 
> Is it possible to refactor this function and
> m2p_remove_override_single() to share some common helper functions?

Yes, I will split those common parts into inline functions and share
them between both implementations.

Roger.

  parent reply	other threads:[~2013-08-01 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 16:07 [PATCH RFC] p2m: use GNTTABOP_unmap_and_duplicate if available Roger Pau Monne
2013-08-01  9:53 ` [Xen-devel] " David Vrabel
2013-08-01 10:21   ` Roger Pau Monné
2013-08-01 10:21   ` Roger Pau Monné [this message]
2013-08-01  9:53 ` David Vrabel

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=51FA36AC.1090609@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano.stabellini@eu.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.