From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: Keir Fraser <keir.xen@gmail.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Backport requests of cs 23420..23423 for 4.0 and 4.1
Date: Mon, 23 Jul 2012 07:01:12 +0200 [thread overview]
Message-ID: <500CDA98.4010205@ts.fujitsu.com> (raw)
In-Reply-To: <5009B336.8000905@eu.citrix.com>
Am 20.07.2012 21:36, schrieb George Dunlap:
> On 19/07/12 22:54, Juergen Gross wrote:
>> Am 19.07.2012 17:11, schrieb Ian Jackson:
>>> Keir Fraser writes ("Re: [Xen-devel] Backport requests of cs
>>> 23420..23423 for 4.0 and 4.1"):
>>>> On 13/07/2012 07:08, "Juergen Gross"<juergen.gross@ts.fujitsu.com>
>>>> wrote:
>>>>> I would like to request to include these changesets in 4.0 and
>>>>> 4.1. The backport is quite trivial, I can send patches if you are
>>>>> willing to take them.
>>>> Will need an Ack from George and then patches applied by (or at
>>>> least an Ack
>>>> from) a tools maintainer.
>>> Thanks for replying Keir, but I'm rather queasy about this.
>>>
>>> These patches have not been in any released version of Xen and are
>>> fairly substantial. I would say that we should not backport anything
>>> that isn't a critical bugfix which hasn't been sitting in a released
>>> version of Xen for a while; and a new feature ought to be considered
>>> very carefully.
>>>
>>> Now maybe the unfortunately extended 4.2 release cycle may mean we
>>> should relax this rule but I'd prefer to see a clear justification for
>>> why this is important to retrofit to 4.1.
>> Live migration is a main high-availability feature of our next release.
>>
>> A performance degradation of 10% and more will not be easily accepted for
>> a system which is expected to be up 24/7.
> Is there a reason you can't just do as XenServer and XCP have done, and
> have them in a local patch queue?
That's plan C. :-)
We are using SLES as base, so plan B is asking Suse...
> Obviously it's better to keep a local patch queue as short as possible,
> but it doesn't seem like you're really going to be that crippled if we
> wait to check them in.
Correct.
I had to try. :-)
Juergen
--
Juergen Gross Principal Developer Operating Systems
PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
prev parent reply other threads:[~2012-07-23 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 6:08 Backport requests of cs 23420..23423 for 4.0 and 4.1 Juergen Gross
2012-07-13 8:05 ` Keir Fraser
2012-07-13 9:26 ` Juergen Gross
2012-07-13 10:07 ` Andrew Cooper
2012-07-19 14:37 ` Keir Fraser
2012-07-19 15:11 ` Ian Jackson
2012-07-19 15:23 ` Keir Fraser
2012-11-05 12:34 ` Pasi Kärkkäinen
2012-07-20 5:54 ` Juergen Gross
2012-07-20 9:26 ` Andrew Cooper
2012-07-20 19:36 ` George Dunlap
2012-07-23 5:01 ` Juergen Gross [this message]
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=500CDA98.4010205@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=keir.xen@gmail.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 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).