From: " Břeťa Vomočil" <only_one_mystery@centrum.cz>
To: <herron.philip@googlemail.com>
Cc: <kvm@vger.kernel.org>
Subject: Re: dividing host CPU performance
Date: Fri, 05 Dec 2008 11:11:40 +0100 [thread overview]
Message-ID: <200812051111.4273@centrum.cz> (raw)
In-Reply-To: <ac07bcaf0812050135p129c8a72pacf1d760adef003e@mail.gmail.com>
>If your hardware supports it you could look into:
>
>http://www.linuxmanpages.com/man8/numactl.8.php
Yes, my HW support it (I have already used it for keeping a VM on specified CPU core), but it doesn't solve the "generic ratio problem". For this case it can be usable - ratio 3:1 on 4-core CPU is simple task with numactl, I agree, but I'm looking for some more generic solution where you can make different ratios, which is not possible to do with numactl (for instance 4:1 on 4 cores).
next prev parent reply other threads:[~2008-12-05 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812050917.10259@centrum.cz>
2008-12-05 8:31 ` dividing host CPU performance Břeťa Vomočil
[not found] ` <ac07bcaf0812050135p129c8a72pacf1d760adef003e@mail.gmail.com>
2008-12-05 10:11 ` Břeťa Vomočil [this message]
2008-12-05 18:55 ` Thomas Besser
2008-12-16 0:14 ` breta
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=200812051111.4273@centrum.cz \
--to=only_one_mystery@centrum.cz \
--cc=herron.philip@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox