All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kaspar <zkaspar82@gmail.com>
To: Brian Jackson <iggy@theiggy.com>
Cc: Dor Laor <dlaor@redhat.com>, kvm@vger.kernel.org
Subject: Re: Windows guest CPU socket/core recognition
Date: Tue, 18 Aug 2009 17:12:42 +0200	[thread overview]
Message-ID: <4A8AC4EA.6070309@gmail.com> (raw)
In-Reply-To: <200908180200.38713.iggy@theiggy.com>

Brian Jackson napsal(a):
> On Monday 17 August 2009 22:28:35 Zdenek Kaspar wrote:
>> Hello everyone,
>>
>> I guess I'm not the first one who hit the problem with Microsoft's
>> licensing model..
>>
>> Nowadays the common single or dual quad-core workstation can't be fully
>> used because it's limited by example: license up to 2 physical
>> processors. Such VM acts like 4-way or 8-way machine.
> 
> 
> Nine times out of ten, a single cpu guest is going to be a better option than 
> a smp/multie core guest. I've seen idle windows guests go from using nearly 
> 200% cpu for -smp 2 to ~5-10% for -smp 1. Unless your guest is actually using 
> all that cpu all the time, you're going to be wasting a decent amount of 
> cycles.

Yes, without proper use it's waste. My guest is 64bit and represents
node in computing cluster working on assigned jobs (not MPI etc..)

>> Is there any way howto expose CPUs differently for this kind of problem?
> 
> 
> There have been patches (from Andre Pryzwara and maybe others) to support 
> multi-core vs mult-socket smp.

I will check these patches, thank you (and Dor Laor) for the hint!

  reply	other threads:[~2009-08-18 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-18  3:28 Windows guest CPU socket/core recognition Zdenek Kaspar
2009-08-18  7:00 ` Brian Jackson
2009-08-18 15:12   ` Zdenek Kaspar [this message]
2009-08-18  7:02 ` Dor Laor
2009-08-18 15:14   ` Andre Przywara

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=4A8AC4EA.6070309@gmail.com \
    --to=zkaspar82@gmail.com \
    --cc=dlaor@redhat.com \
    --cc=iggy@theiggy.com \
    --cc=kvm@vger.kernel.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 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.