All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Ian Pratt <Ian.Pratt@eu.citrix.com>
Cc: James Harper <james.harper@bendigoit.com.au>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Poor HVM performance with 8 vcpus
Date: Wed, 07 Oct 2009 10:31:05 +0200	[thread overview]
Message-ID: <4ACC51C9.5080408@ts.fujitsu.com> (raw)
In-Reply-To: <4FA716B1526C7C4DB0375C6DADBC4EA342A68E5C95@LONPMAILBOX01.citrite.net>

Ian Pratt wrote:
>  
>> Are there any other of these heuristics tucked away in xen? Would there
>> be any benefit to specifying the OS being virtualised in the config? Eg
>> "os=windows"?
> 
> That's really the only one that springs to mind.
> 
> Given how simple a predictor would be, I think that's the best approach.
> 
> Setting the OS in the config file is a little tricky as in a couple of instances you'd want to know the exact version (linux moved the 64b direct mapped region at some point during 2.6 development).

I think it is a bad idea in most cases to use such a basic parameter like
"os=xyz" to tune some specific behaviour. It may be useful to set some default
parameters, but there should be an explicit parameter as well, e.g.
"shadow_heuristic=direct-mapped@address"


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 636 47950
Fujitsu Technolgy Solutions               e-mail: juergen.gross@ts.fujitsu.com
Otto-Hahn-Ring 6                        Internet: ts.fujitsu.com
D-81739 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2009-10-07  8:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07  6:55 Poor HVM performance with 8 vcpus Juergen Gross
2009-10-07  7:26 ` Keir Fraser
2009-10-07  7:49   ` Juergen Gross
2009-10-07  7:56 ` Ian Pratt
2009-10-07  8:08   ` James Harper
2009-10-07  8:13     ` Ian Pratt
2009-10-07  8:31       ` Juergen Gross [this message]
2009-10-07  8:17     ` Keir Fraser
2009-10-07  9:12     ` Tim Deegan
2009-10-07  9:40       ` Juergen Gross
2009-10-07 10:11         ` George Dunlap
2009-10-07 11:45           ` Juergen Gross
2009-10-07 13:44             ` George Dunlap
     [not found]             ` <de76405a0910070627s7585c587l8753e40d1d2b77b9@mail.gmail.com>
     [not found]               ` <4ACC9C40.3030503@ts.fujitsu.com>
2009-10-07 14:24                 ` George Dunlap
2009-10-08  5:00                   ` Juergen Gross
2009-10-07 10:14         ` Tim Deegan
2009-10-07 12:32           ` Juergen Gross
2009-10-07 16:37 ` Gianluca Guida
2009-10-08  7:10   ` Juergen Gross
2009-10-14  8:16     ` Juergen Gross
2009-10-14  8:35       ` Keir Fraser
2009-10-14  9:11         ` Juergen Gross
2009-10-14 10:16         ` Gianluca Guida
2009-10-14 10:44           ` Juergen Gross
2009-10-14 10:49             ` Keir Fraser
2009-10-14  8:41       ` Tim Deegan
2009-10-14  9:17         ` Juergen Gross
2009-10-14 11:35       ` Gianluca Guida
2009-10-14 11:43         ` Juergen Gross

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=4ACC51C9.5080408@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --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 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.