On 19.11.2013 20:18, yunhong jiang wrote:
On Tue, 2013-11-19 at 12:52 +, Daniel P. Berrange wrote:
On Wed, Nov 13, 2013 at 02:46:06PM +0200, Tuomas Paappanen wrote:
Hi all,
I would like to hear your thoughts about core pinning in Openstack.
Currently nova(with qemu-kvm) supports usage of
On Wed, Nov 27, 2013 at 03:50:47PM +0200, Tuomas Paappanen wrote:
On Tue, 2013-11-19 at 12:52 +, Daniel P. Berrange wrote:
I think there are several use cases mixed up in your descriptions
here which should likely be considered independantly
- pCPU/vCPU pinning
I don't really
Hi Roman,
I haven't but I will write a blueprint for the core pinning part.
I considered vcpu element usage as well but in that case you can not set
e.g. vcpu-0 to run on pcpu-0. Vcpus and emulator are sharing all pcpus
defined in cpuset so I decided to use cputune element.
Are you using
On Wed, Nov 13, 2013 at 02:46:06PM +0200, Tuomas Paappanen wrote:
Hi all,
I would like to hear your thoughts about core pinning in Openstack.
Currently nova(with qemu-kvm) supports usage of cpu set of PCPUs
what can be used by instances. I didn't find blueprint, but I think
this feature is
On Wed, Nov 13, 2013 at 11:57:22AM -0600, Chris Friesen wrote:
On 11/13/2013 11:40 AM, Jiang, Yunhong wrote:
But, from performance point of view it is better to exclusively
dedicate PCPUs for VCPUs and emulator. In some cases you may want
to guarantee that only one instance(and its VCPUs) is
On Tue, 2013-11-19 at 12:52 +, Daniel P. Berrange wrote:
On Wed, Nov 13, 2013 at 02:46:06PM +0200, Tuomas Paappanen wrote:
Hi all,
I would like to hear your thoughts about core pinning in Openstack.
Currently nova(with qemu-kvm) supports usage of cpu set of PCPUs
what can be used
Tuomas,
Have you published your code/blueprints anywhere? Looks like we’re working on
the same stuff. I have implemented almost the same feature set (haven’t
published anything yet because of this thread), except for the scheduler part.
The main goal is to be able to pin VCPUs in NUMA
Hi,
The use cases fro CPU pinning are exactly like discussed above: (1)
lowering guest scheduling latencies and (2) improving networking latencies
by pinning the SR-IOV IRQ's to specific cores. There is also a third use
case, (3) avoiding long latencies with spinlocks.
On Wed, Nov 13, 2013 at
On 13.11.2013 20:20, Jiang, Yunhong wrote:
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: Wednesday, November 13, 2013 9:57 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Core pinning
On 11/13/2013 11:40 AM, Jiang
-Original Message-
From: Tuomas Paappanen [mailto:tuomas.paappa...@tieto.com]
Sent: Wednesday, November 13, 2013 4:46 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova] Core pinning
Hi all,
I would like to hear your thoughts about core pinning
On 11/13/2013 11:40 AM, Jiang, Yunhong wrote:
But, from performance point of view it is better to exclusively
dedicate PCPUs for VCPUs and emulator. In some cases you may want
to guarantee that only one instance(and its VCPUs) is using certain
PCPUs. By using core pinning you can optimize
-Original Message-
From: Chris Friesen [mailto:chris.frie...@windriver.com]
Sent: Wednesday, November 13, 2013 9:57 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] Core pinning
On 11/13/2013 11:40 AM, Jiang, Yunhong wrote:
But, from performance
12 matches
Mail list logo
