xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
	Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Even faster page copy for Xen?
Date: Fri, 16 Jul 2010 08:57:37 +0100	[thread overview]
Message-ID: <C865CF81.1AD3F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <bf4d73f4-7a43-40d4-b362-c4797d5b0678@default>

Jan also added a copy_page hypercall, so he may have been optimising for
that, since I guess the Novell kernels must use it.

 -- Keir

On 16/07/2010 00:36, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> I wasn't sure about that... Jan's patch to speed up
> copy_page (by 12%) went in before tmem was in-tree,
> so I assumed otherwise.  Clearly my interest is for
> tmem, especially if 2x-4x improvement is possible,
> but if there really is no significant advantage for
> non-tmem code, I will put it on my list... for sometime
> in the next century when I am a good x86 assembly
> programmer :-)
> 
>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
>> Sent: Thursday, July 15, 2010 3:35 PM
>> To: Dan Magenheimer; Jan Beulich
>> Cc: xen-devel@lists.xensource.com
>> Subject: Re: Even faster page copy for Xen?
>> 
>> It has to be said, possibly tmem excepted, there is very little page
>> copying
>> in Xen.
>> 
>>  -- Keir
>> 
>> On 15/07/2010 19:15, "Dan Magenheimer" <dan.magenheimer@oracle.com>
>> wrote:
>> 
>>> Hi Jan, Keir --
>>> 
>>> My x86 assembly skills are much too poor to carefully evaluate
>>> and, if of value, implement this in Xen but given your previous
>>> interest, such as:
>>> 
>>> http://xenbits.xensource.com/xen-unstable.hg?rev/8de4b4e9a435
>>> 
>>> the following might be worth looking at.
>>> 
>>> Intel has just posted memcpy improvements for glibc for recent
>>> popular Intel processor families here:
>>> 
>>> http://article.gmane.org/gmane.comp.lib.glibc.alpha/15278
>>> 
>>> The preface to the above patch looks very enticing...
>>> 
>>> Semi-related, I wonder if you know, if there were a
>>> "copy_page_from_other_node()" to be used if the
>>> caller is fairly sure that the page is being copied
>>> between nodes, could this be made significantly faster
>>> than a normal copy_page()?
>>> 
>>> Thanks,
>>> Dan
>> 
>> 

  reply	other threads:[~2010-07-16  7:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 18:15 Even faster page copy for Xen? Dan Magenheimer
2010-07-15 21:35 ` Keir Fraser
2010-07-15 23:36   ` Dan Magenheimer
2010-07-16  7:57     ` Keir Fraser [this message]
2010-08-06  7:57 ` Jan Beulich
2010-08-09 17:47   ` Dulloor
2010-08-09 17:57     ` Dulloor
2010-08-10  6:24       ` Jan Beulich
2010-08-10 12:31         ` Dan Magenheimer
2010-08-10 12:41           ` Keir Fraser
2010-08-10 12:46           ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2010-08-05 17:48 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=C865CF81.1AD3F%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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).