From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Even faster page copy for Xen?
Date: Thu, 15 Jul 2010 11:15:46 -0700 (PDT) [thread overview]
Message-ID: <b39a30eb-01ee-46e4-83c4-2e1b6116929e@default> (raw)
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
next reply other threads:[~2010-07-15 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 18:15 Dan Magenheimer [this message]
2010-07-15 21:35 ` Even faster page copy for Xen? Keir Fraser
2010-07-15 23:36 ` Dan Magenheimer
2010-07-16 7:57 ` Keir Fraser
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=b39a30eb-01ee-46e4-83c4-2e1b6116929e@default \
--to=dan.magenheimer@oracle.com \
--cc=JBeulich@novell.com \
--cc=keir.fraser@eu.citrix.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).