From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, Dario Faggioli <raistlin@linux.it>
Cc: Andre Przywara <andre.przywara@amd.com>,
Anil Madhavapeddy <anil@recoil.org>,
George Dunlap <dunlapg@gmail.com>,
xen-devel <xen-devel@lists.xen.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Yang ZZhang <yang.z.zhang@intel.com>
Subject: Re: NUMA TODO-list for xen-devel
Date: Mon, 6 Aug 2012 09:28:25 -0700 (PDT) [thread overview]
Message-ID: <566f060d-e29e-4b49-9746-1154873062bf@default> (raw)
In-Reply-To: <501F8B250200007800092C62@nat28.tlf.novell.com>
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Subject: RE: [Xen-devel] NUMA TODO-list for xen-devel
>
> >>> On 04.08.12 at 00:34, Dan Magenheimer <dan.magenheimer@oracle.com> wrote:
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> The question is whether trading functionality for performance
> >> is an acceptable choice.
> >
> > If there were a lwn.net equivalent for Xen, I'd be pushing to get
> > quoted on the following:
> >
> > "Virtualization: You can have flexibility or you can have performance.
> > Pick one."
> >
> > A couple of years ago when NUMA was first being extensively discussed
> > for Xen, I suggested that this should really be a "top level" flag
> > that a sysadmin should be able to select: Either optimize for
> > performance or optimize for flexibility. Then Xen and the Xen tools
> > should "do the right thing" depending on the selection.
> >
> > I still think this is a good way to surface the tradeoffs for
> > a very complex problem to the vast majority of users/admins.
> > Clearly they will want "both" but forcing the choice will
> > provoke more thought about their use model, as well as provide
> > important guidance to the underlying implementations.
>
> I would expect a good part to pick performance, and then
> go whine about something not working in an emergency. On
> xen-devel one could respond with this-is-what-you-get, but
> you can't necessarily do so to paying customers...
Well, you can, but you have to first convince marketing that
virtualization doesn't solve all problems for all users all the
time. :-)
The two options would have to be clearly documented as:
"flexibility-is-my-highest-priority-and-performance-is-second-priority"
and
"performance-is-my-highest-priority-and-flexibility-is-second-priority"
and when a user selects the latter, they should be prompted with
"Are you really sure you want to use virtualization instead of bare metal?"
Sigh. We can only wish.
Dan
next prev parent reply other threads:[~2012-08-06 16:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 16:16 NUMA TODO-list for xen-devel Dario Faggioli
2012-08-01 16:24 ` Dario Faggioli
2012-08-01 16:30 ` Andrew Cooper
2012-08-01 16:47 ` Dario Faggioli
2012-08-01 16:53 ` Andrew Cooper
2012-08-02 9:40 ` Jan Beulich
2012-08-02 13:21 ` Dario Faggioli
2012-08-01 16:32 ` Anil Madhavapeddy
2012-08-01 16:58 ` Dario Faggioli
2012-08-02 0:04 ` Malte Schwarzkopf
2012-08-07 23:53 ` Dario Faggioli
2012-08-02 1:04 ` Zhang, Yang Z
2012-08-07 22:56 ` Dario Faggioli
2012-08-02 9:43 ` Jan Beulich
2012-08-02 13:34 ` Dario Faggioli
2012-08-02 14:07 ` Jan Beulich
2012-08-02 16:36 ` George Dunlap
2012-08-03 9:23 ` Jan Beulich
2012-08-03 9:48 ` Andre Przywara
2012-08-03 10:03 ` Jan Beulich
2012-08-03 22:40 ` Dan Magenheimer
2012-08-03 11:00 ` George Dunlap
2012-08-03 22:34 ` Dan Magenheimer
2012-08-06 7:15 ` Jan Beulich
2012-08-06 16:28 ` Dan Magenheimer [this message]
2012-08-03 10:02 ` Andre Przywara
2012-08-03 10:40 ` Jan Beulich
2012-08-03 11:26 ` Andre Przywara
2012-08-03 11:38 ` Jan Beulich
2012-08-03 13:14 ` Dario Faggioli
2012-08-03 13:52 ` Jan Beulich
2012-08-03 22:42 ` Dan Magenheimer
2012-08-08 7:07 ` Dario Faggioli
2012-08-08 7:43 ` Dario Faggioli
2012-08-03 22:22 ` Dan Magenheimer
2012-08-07 23:49 ` Dario Faggioli
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=566f060d-e29e-4b49-9746-1154873062bf@default \
--to=dan.magenheimer@oracle.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=anil@recoil.org \
--cc=dunlapg@gmail.com \
--cc=raistlin@linux.it \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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).