From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xen.org
Subject: Re: PV performance degraded after live migration
Date: Thu, 16 Mar 2017 09:13:06 +0100 [thread overview]
Message-ID: <20170316081306.GB8408@aepfle.de> (raw)
In-Reply-To: <58C9762302000078001436DE@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 250 bytes --]
On Wed, Mar 15, Jan Beulich wrote:
> ..., and iirc PV migration didn't have any issue with TSC freq
> changing during migration prior to the introduction of vTSC.
When was this introduced? There is a claim that this slowdown is a
regression.
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-16 8:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 11:20 PV performance degraded after live migration Olaf Hering
2017-03-15 11:30 ` Andrew Cooper
2017-03-15 14:52 ` Olaf Hering
2017-03-15 15:23 ` Olaf Hering
2017-03-15 15:26 ` Andrew Cooper
2017-03-15 15:33 ` Juergen Gross
2017-03-15 15:43 ` Boris Ostrovsky
2017-03-15 15:53 ` Juergen Gross
2017-03-15 16:13 ` Jan Beulich
2017-03-16 8:13 ` Olaf Hering [this message]
2017-03-16 10:20 ` Jan Beulich
2017-03-15 16:02 ` Jan Beulich
2017-03-15 16:41 ` Boris Ostrovsky
2017-03-15 16:50 ` Jan Beulich
2017-03-15 15:43 ` Alan Robinson
2017-03-15 15:51 ` Andrew Cooper
2017-03-15 15:53 ` Jan Beulich
2017-03-15 15:56 ` Alan Robinson
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=20170316081306.GB8408@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.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.