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>, Dulloor <dulloor@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: Even faster page copy for Xen?
Date: Tue, 10 Aug 2010 13:41:17 +0100	[thread overview]
Message-ID: <C887077D.1D463%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <8e0efd21-1863-489c-a58a-317f69646a3b@default>

On 10/08/2010 13:31, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

>> You can do so if you feel like saving/restoring all necessary XMM
>> state isn't going to eat up all of the performance win...
> 
> Again excuse my x86 ignorance, but on some architectures
> floating point registers can be saved/restored "lazily"
> because there is a privileged bit that disables their use
> (which can be trapped and used as a "floating-point dirty" bit).
> Is there anything equivalent for the XMM state?  If so,
> then lazy save might be a good approach.  If not, then I agree
> that the state save/restore overhead might eat up the performance
> win.  (However, if we were to later use Linux memory compaction
> and NUMA page migration, the performance tradeoff might change
> to positive.)

We do lazy FPU/SSE restore already. But in any case, it is questionable how
much faster you can make a non-temporal and/or non-local bulk memory copy:
it ought to be bottlenecked on FSB bandwidth.

 -- Keir

  reply	other threads:[~2010-08-10 12:41 UTC|newest]

Thread overview: 11+ 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
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 [this message]
2010-08-10 12:46           ` 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=C887077D.1D463%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=dulloor@gmail.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).