From: Grant McWilliams <grantmasterflash@gmail.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
xen-devel@lists.xensource.com,
Keir Fraser <Keir.Fraser@eu.citrix.com>,
Joanna Rutkowska <joanna@invisiblethingslab.com>
Subject: Re: New release candidate for Xen 4.0.0 (RC9)
Date: Wed, 31 Mar 2010 15:55:15 -0400 [thread overview]
Message-ID: <m2ged123fa31003311255g7def6f64u64d90f8ec8181c9b@mail.gmail.com> (raw)
In-Reply-To: <a0d1288d-7059-4836-84e6-802ad67d9feb@default>
[-- Attachment #1.1: Type: text/plain, Size: 840 bytes --]
Grant McWilliams
Some people, when confronted with a problem, think "I know, I'll use
Windows."
Now they have two problems.
> pvops is certainly where the development effort is currently focussed,
> > and hopefully what the commercial distros will all be using later this
> > year[*].
>
> Yes, agreed. This is definitely the direction. But I don't
> think it's time to throw away linux-2.6.18-xen.hg quite yet
> (the suggestion of which is what triggered my allergic reaction
> here :-).
>
>
Do we yet have any real numbers on the performance hit with the move to
pvops? We HAVE to at some point move but I think part of the decision on
WHEN to move will be based on this. I've seen various messages over the
years about "we have to sit down and figure out how big the hit is and what
to do about it".
Just curious.
Grant McWilliams
[-- Attachment #1.2: Type: text/html, Size: 1191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-31 19:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:27 New release candidate for Xen 4.0.0 (RC9) Keir Fraser
2010-03-31 10:07 ` Joanna Rutkowska
2010-03-31 10:54 ` Keir Fraser
2010-03-31 11:00 ` Joanna Rutkowska
2010-03-31 11:13 ` Keir Fraser
2010-03-31 12:38 ` Ian Pratt
2010-03-31 14:20 ` Dan Magenheimer
2010-03-31 14:32 ` Keir Fraser
2010-03-31 14:44 ` Ian Pratt
2010-03-31 19:55 ` Grant McWilliams [this message]
2010-03-31 15:02 ` Bastian Blank
2010-03-31 15:09 ` Keir Fraser
2010-03-31 15:44 ` Bastian Blank
2010-03-31 16:38 ` Keir Fraser
2010-03-31 18:03 ` Konrad Rzeszutek Wilk
2010-03-31 18:18 ` Keir Fraser
2010-03-31 20:40 ` Jeremy Fitzhardinge
2010-03-31 19:10 ` Konrad Rzeszutek Wilk
2010-03-31 19:33 ` Keir Fraser
2010-03-31 19:52 ` Konrad Rzeszutek Wilk
2010-03-31 20:07 ` Keir Fraser
2010-03-31 21:07 ` Konrad Rzeszutek Wilk
2010-05-19 12:10 ` Keir Fraser
2010-05-26 15:02 ` Konrad Rzeszutek Wilk
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=m2ged123fa31003311255g7def6f64u64d90f8ec8181c9b@mail.gmail.com \
--to=grantmasterflash@gmail.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=joanna@invisiblethingslab.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).