From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Peter Maloney <peter.maloney@brockmann-consult.de>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 4.1.2 very slow without upstream patches, but fast with them, also 4.2 very slow
Date: Mon, 6 Aug 2012 11:24:45 +0100 [thread overview]
Message-ID: <501F9B6D.10706@citrix.com> (raw)
In-Reply-To: <501F98A1.4070806@brockmann-consult.de>
On 06/08/12 11:12, Peter Maloney wrote:
> my AMD FX-8150 system with vanilla source code is super slow, both the
> dom0 and domUs. However, after I merge the upstream patches I found in
> the openSUSE rpm, it runs normally.
>
> I tried 4.2-unstable and it was the same. There was no rc1 when I tested
> it about 1.5 weeks ago. And 4.2 has the same horrible performance, and
> obviously those patches won't work any more since the 4.2 code looks
> completely reorganized, so I'm stuck with 4.1.2
>
> Here is the rpm I was using at the time:
> http://download.opensuse.org/update/12.1/src/xen-4.1.2_16-1.7.1.src.rpm
>
> To see the list of the patches and what order to apply them, see the
> spec file.
>
> Please make sure this performance issue is fixed for the 4.2 release.
> And I would be happy to test whatever files you send me.
>
Without identifying which patch or patches make a difference for you,
there is very little we can do. There are 406 patches in that spec
file. Furthermore, from the file names, I would say that most of the
patches have been backported from unstable.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2012-08-06 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 10:12 4.1.2 very slow without upstream patches, but fast with them, also 4.2 very slow Peter Maloney
2012-08-06 10:24 ` Andrew Cooper [this message]
2012-08-06 10:31 ` Jan Beulich
2012-08-07 7:25 ` Peter Maloney
2012-08-13 18:54 ` Peter Maloney
2012-08-13 20:59 ` Peter Maloney
2012-10-03 17:19 ` Peter Maloney
2012-10-03 20:05 ` Peter Maloney
2012-10-04 14:25 ` Konrad Rzeszutek Wilk
2012-10-05 20:19 ` Peter Maloney
2012-10-06 8:36 ` Peter Maloney
2012-08-06 12:41 ` Malcolm Crossley
2012-08-06 14:02 ` Konrad Rzeszutek Wilk
[not found] ` <20120806140226.GB3093@phenom.dumpdata.com>
2012-08-07 21:42 ` M A Young
[not found] ` <alpine.DEB.2.00.1208072239120.8441@vega-c.dur.ac.uk>
2012-08-07 22:21 ` W. Michael Petullo
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=501F9B6D.10706@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=peter.maloney@brockmann-consult.de \
--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 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).